Skip to main content
Glama

Get the resume PDF link

get_resume_document
Read-only

Use this when a resume PDF link has expired or the user asks for the link again: renews the private signed link to the same PDF, valid up to one hour, without another adaptation or charge.

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": {
      "guestToken": "<guestToken>",
      "operationId": "<operationId>"
    },
    "name": "get_resume_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
operationIdYes

Output Schema

NameRequiredDescriptionDefault
downloadUrlYes
expiresInSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description adds genuinely new behavior: the link is private and signed, is valid for up to one hour, and renewal causes no additional adaptation or charge. It stops short of saying whether renewal invalidates previously issued links or what happens when the current link is still valid.

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?

A single sentence that front-loads the trigger ('Use this when...') and then the effect, with no filler or restatement of the title. Every clause adds information: expiry condition, link privacy, validity window, and no extra charge.

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?

An output schema exists, so return values need not be explained, and the safety profile is covered by annotations. However, for a two-parameter tool with no schema descriptions, the definition should say what the parameters carry and whether renewal requires the guest context to still be valid; that omission leaves the call under-specified.

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

Parameters2/5

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

Schema description coverage is 0% and both required parameters (guestToken, operationId) are undocumented in the schema, yet the description never mentions either one. The agent must infer that guestToken is the guest auth token and operationId identifies the resume operation, which is a meaningful gap for the only two inputs the tool takes.

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?

States a specific verb and resource: it renews the private signed link to the same resume PDF. The title ('Get the resume PDF link') suggests a plain fetch, but the description corrects that to a renewal of the existing link, so an agent knows exactly what the call produces and that it is not a re-render or re-adaptation.

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

Usage Guidelines4/5

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

Gives explicit trigger conditions: an expired PDF link, or a user asking for the link again. No when-not cases or named alternatives are given, but among the sibling tools none plausibly overlaps with link renewal, so the guidance is sufficient in practice.

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