fps-cv-mcp

get_cv_sections

Read-onlyIdempotent

Retrieve one or more CV sections in a single call, with optional semantic enrichments. Unrecognized names are reported with the available section list.

Instructions

Retrieve one or more CV sections in a single call.

Accepts a list of section names. Returns all matched sections separated by blank lines. Reports any unrecognized names with the list of available sections.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`enrich`	No	Include semantic enrichments (cross-references, skill levels)
`section_names`	Yes	One or more section names to retrieve (case-insensitive, '&' ignored). Use list_cv_sections() to see available names.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9Sep 16, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds behavioral detail: returns sections separated by blank lines and reports unrecognized names with the list of available sections. This goes beyond annotations and helps the agent know what to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences that front-load the purpose and then detail behavior. No fluff or redundancy, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core behavior: input, output format, and error reporting. Combined with full schema coverage and an output schema, it's sufficient for an agent to call it correctly. It also hints at using list_cv_sections for available names via the schema parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema parameter descriptions are detailed (case-insensitive, '&' ignored, list_cv_sections reference). The main description doesn't add parameter details, but the schema already covers them, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'Retrieve' and resource 'CV sections', and specifies it can fetch one or more sections in a single call. This distinguishes it from siblings like list_cv_sections (which lists names) and get_cv (which returns the entire CV), so an agent can tell them apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. It implies usage for retrieving specific sections, but without guidance on when not to use it. The only hint is in the schema parameter description referencing list_cv_sections, which is not part of the main description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server