CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastmcp-server

Build, extend, or review MCP servers with Python FastMCP, using documentation matched to the project's version.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs/.mintlify/skills/fastmcp-server/SKILL.md

The canonical home for this skill is fastmcp-server in PrefectHQ/fastmcp

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-organized, expert-level body that consistently provides FastMCP-specific, non-obvious guidance with explicit verification steps. The main gaps are the absence of any executable code example, a few generic advisory sentences, and content long enough that some sections could be split into reference files.

Suggestions

Add one minimal executable example, such as an in-process verification snippet using fastmcp's Client against a server instance, or ToolError usage for client-facing failures.

Trim generic guidance Claude already knows (e.g., "Give clients enough context to use results and recover from errors", "The right granularity depends on the service") to tighten token efficiency.

Consider moving the agent-workflow evaluation guidance into a separate reference file linked from a short overview section, keeping SKILL.md as a lean index.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence, delivering non-obvious FastMCP-specific gotchas ("With mask_error_details=True, ordinary exceptions such as ValueError lose their messages") rather than generic explanations. A few advisory sentences like "Give clients enough context to use results and recover from errors" state things Claude already knows and could be trimmed, keeping it below the lean 5 anchor.

4 / 5

Actionability

Guidance names concrete, checkable identifiers: "ToolError, ResourceError, or PromptError from fastmcp.exceptions", "functools.wraps", "Literal or enums", the "Client" for in-process testing, and the llms.txt docs index. As an instruction-only skill this is largely executable guidance, but a small code snippet (e.g., an in-process Client verification or ToolError usage) is missing, leaving minor gaps versus the copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

A clear macro sequence (check installed version and docs → author the interface → verify via Client → evaluate agent workflows) with explicit validation checkpoints ("check the outcome against independent API or database evidence", "a meaningful failure"). It is presented as topical prose rather than an explicit step/checklist format with feedback loops, so it sits between the 4 and 5 anchors.

4 / 5

Progressive Disclosure

No bundle files exist, and the body is organized into three well-signaled sections that point to the authoritative external reference (the versioned docs index, "Read the version-matched Skills docs from the index"). At ~90 lines, content such as the agent-evaluation guidance could arguably live in a separate reference file, which keeps it below the ideal 5 split.

4 / 5

Total

16

/

20

Passed

Description

70%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.

A concise, specific description that clearly states what the skill does and occupies a distinct niche. Its main weakness is the absence of explicit "when to use" trigger guidance, which caps completeness and leaves natural trigger phrases implicit.

Suggestions

Add an explicit trigger clause, e.g., "Use when building or modifying MCP servers, or when the user mentions FastMCP, MCP servers, or the Model Context Protocol."

Include the spelled-out term "Model Context Protocol" and common variants (e.g., "MCP tool server") so the description matches how users naturally phrase the request.

Optionally enumerate the main capability areas (tools, resources, prompts, auth, transports) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Build, extend, or review MCP servers with Python FastMCP" names the domain and three concrete actions, and "documentation matched to the project's version" adds a concrete method. It stops short of the 5 anchor's comprehensive multi-capability enumeration (e.g., tools/resources/prompts), but is well above the 1-2-action level of 3.

4 / 5

Completeness

The "what" is clear (build, extend, or review MCP servers with FastMCP), but there is no "Use when..." clause or equivalent explicit trigger guidance; "using documentation matched to the project's version" describes method, not timing. Per the rubric guideline, a missing trigger clause caps completeness at 3, and it is not below 3 because the what is fully explicit.

3 / 5

Trigger Term Quality

"MCP servers" and "Python FastMCP" are the natural phrases users would say for this need, giving good keyword coverage. Common variations like the spelled-out "Model Context Protocol" or "tool server" are missing, so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"MCP servers with Python FastMCP" pins a specific framework and task niche with distinct triggers, carrying minimal conflict risk with generic Python or documentation skills. It fits the clear-niche 5 anchor better than the 4 anchor's minor-overlap example.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PrefectHQ/fastmcp

Path

docs/.mintlify/skills/fastmcp-server/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.