Skip to main content
Glama

PDF download link

export_pdf
Read-onlyIdempotent

Use this when the person asks for their resume as a PDF or asks to download it. Returns a link that opens the resume's download page on cvember.com. Nothing is bought through this tool.

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": {
      "resumeId": "<resumeId>"
    },
    "name": "export_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYesA resume id from list_resumes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the result is a link to an external download page on cvember.com rather than file bytes, and no purchase is involved. It omits whether a PDF is generated on demand or whether links expire.

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

Conciseness4/5

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

Three short sentences, front-loaded with the usage trigger, then the return behavior, then a clarifying scope note. Minor waste in the final sentence about purchases, which is useful only against an unstated checkout flow.

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

Completeness3/5

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

For a single-parameter read tool with no output schema, the description covers the trigger and the shape of the result, which is close to sufficient. It stops short of describing link lifetime or whether the returned URL requires an authenticated browser session.

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 single resumeId parameter is fully documented in the schema, including its source (list_resumes). The description adds nothing about the parameter, so the baseline of 3 applies.

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

Purpose4/5

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

The description states a concrete verb+resource: it returns a link to the resume's PDF download page on cvember.com. It doesn't explicitly contrast with get_resume, which an agent might otherwise pick for 'get my resume', so sibling differentiation is only implicit.

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?

It gives a clear trigger ('when the person asks for their resume as a PDF or asks to download it'), which is useful. It offers no exclusion or alternative — e.g. when to prefer get_resume for viewing content versus this tool for downloading — leaving that routing to inference.

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