CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

call-mcp-tool

Call MCP server tool for extended capabilities. Check 'MCP Servers' section in system prompt for available servers and tools. When you need to use external service or access specialized functionality.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/system/call-mcp-tool/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-organized reference for a single-purpose skill: complete parameter documentation, a concrete JSON example, and clean sectioning with no padding or over-explanation. The only weakness is minor gaps in actionability around discovering server/tool identifiers and handling results. Strong result overall.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero concept explanations or padding: a one-line summary, a parameter table, a single usage pointer, one example, and related skills — every token earns its place.

5 / 5

Actionability

The parameter table (types, required flags, defaults) plus a copy-paste JSON example give mostly executable guidance, but there are minor gaps: no indication of how to discover valid server identifiers or tool names beyond deferring to the system prompt, and no result/error handling guidance.

4 / 5

Workflow Clarity

This is a simple single-task skill and the single action — call a tool with server, tool_name, and arguments — is fully unambiguous given the parameter table and example, so the simple-skill exception applies; no destructive or batch cap is triggered.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files (none exist in the bundle, and no dangling references are made); the Parameters, Usage, Examples, and Related Skills sections are well organized.

5 / 5

Total

19

/

20

Passed

Description

45%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the MCP domain but leans on generic filler ('extended capabilities', 'specialized functionality') instead of concrete actions or trigger phrases. Both the 'what' and the 'when' are present yet vague, and the broad wording creates overlap risk with other integration skills. It sits at or slightly below the midpoint of the rubric.

Suggestions

Replace 'for extended capabilities' with concrete actions, e.g. 'Invoke tools exposed by MCP servers, passing structured arguments and returning tool results.'

Make the 'when' clause specific with natural trigger phrases, e.g. 'Use when a task requires a tool exposed by a connected MCP server — e.g. searching, fetching data, or querying an external service.'

Add natural trigger terms and synonyms ('MCP tools', 'external tool', server-specific keywords) so the description is distinguishable from generic external-service skills.

DimensionReasoningScore

Specificity

The description names the MCP domain but the only action offered is the generic 'Call MCP server tool for extended capabilities', where 'extended capabilities' is pure filler; no concrete actions are enumerated.

2 / 5

Completeness

A 'when' clause exists ('When you need to use external service or access specialized functionality') but both the what ('extended capabilities') and the when are vague; it does not reach anchor 4 because the 'what' lacks a clear, concrete statement of capability.

3 / 5

Trigger Term Quality

It includes some relevant keywords ('MCP server', 'tools', 'external service') but misses common natural variations and synonyms a user would actually say, and 'specialized functionality' is jargon-adjacent filler.

3 / 5

Distinctiveness Conflict Risk

The MCP niche is somewhat specific, but the broad phrasing 'external service or access specialized functionality' could overlap with many other integration or tool-invocation skills.

3 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

openakita/openakita

Path

skills/system/call-mcp-tool/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.