Retrieve a resume by ID or get your most recent resume.
Get a resume by ID or get the most recent resume if no ID provided
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_resume"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| resume_id | No | Resume ID (optional, defaults to most recent) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the default behavior (most recent resume if no ID), but does not mention what data the response contains, authentication requirements, or any mutation side effects. This is moderate transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence that conveys the main purpose and conditional behavior without any filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool lacks an output schema, but the description does not describe the return value (e.g., full resume object, metadata). Given the complexity of the domain and many sibling tools, this omission leaves a gap in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter description already states 'optional, defaults to most recent'. The tool description repeats this, adding no new meaning beyond the schema. Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('resume') and clearly explains the two distinct behaviors: retrieve by ID or default to most recent. This distinguishes it from sibling tools like 'list_resumes' which returns multiple resumes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to provide an ID (to get a specific resume) versus when not (to get the most recent), but it does not explicitly contrast with similar tools like 'get_resume_docx_url' or 'get_resume_pdf_url', leaving the agent to infer when to use this tool over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.