Skip to main content
Glama

download_resume_api_resume_download_get

Download Resume

Download the user's resume.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

Example Response:

{
  "success": true
}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "s3Path": "<s3Path>"
    },
    "name": "download_resume_api_resume_download_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
s3PathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only provides a minimal success response example and does not explain what 'download' means (e.g., returns a file, a URL, or just status) or why s3Path is required. Key traits like side effects or permissions are absent.

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

Conciseness3/5

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

The description is not overly long, but the heading 'Download Resume' is redundant with the following sentence. The response section is front-loaded and useful, though the overall structure could better prioritize explaining the parameter.

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

Completeness2/5

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

For a simple GET tool with one required parameter and no output schema or annotations, the description should clarify the s3Path requirement and the nature of the response. It fails to do so, leaving an agent unable to call the tool correctly with confidence.

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

Parameters1/5

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

The sole parameter s3Path has 0% schema description coverage and the description never mentions it or explains its role, format, or relevance to downloading a resume. This leaves the required parameter entirely undocumented.

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

Purpose2/5

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

The description restates the tool name with 'Download Resume' and 'Download the user's resume,' adding almost no distinguishing detail beyond the name. It does not differentiate from sibling tools like get_resume_api_resume_get or get_rendercv_pdf_download.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as get_resume or get_rendercv_pdf_download. The description gives no context about the scenario or prerequisites for choosing this download endpoint.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources