Skip to main content
Glama

Switch the resume design

render_resume_template
Idempotent

Use this when the user wants the same tailored resume in another Matchaa template: renders a new private PDF from the latest revision with exactly the same content, without another adaptation or AI call. Pass the latest operationId. Identical retries reuse the export.

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>",
      "templateId": "<templateId>"
    },
    "name": "render_resume_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
templateIdYes
operationIdYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that output is a private PDF built from the latest revision, that no AI call or adaptation is incurred, and that identical retries reuse the existing export. That last point explains the mechanism behind idempotentHint=true rather than merely restating it, and the 'private' qualifier adds access-scope context the annotations do not carry. No contradiction with readOnlyHint=false or destructiveHint=false.

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?

Three short sentences, front-loaded with the trigger condition, then the effect, then the parameter and retry note. Nothing is repeated from the name or title and no sentence is padding.

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

Completeness4/5

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

With an output schema present, the description need not describe the returned document, and it correctly focuses on when to call, what is produced, and idempotency. The main residual gap is how a caller obtains a valid templateId or what guestToken represents, which matters for a 3-required-parameter tool with zero schema coverage.

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%, so the description carries the full burden, yet it meaningfully covers only one of three parameters: operationId, where 'latest' usefully tells the caller which operation to pass. guestToken is never mentioned at all, and templateId is only waved at as 'another Matchaa template' with no hint that it is a constrained enum of 19 designs or how to discover valid values (e.g., list_resume_templates).

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?

The description states a specific verb and resource ('renders a new private PDF from the latest revision') and pins down the scope: identical content, no re-adaptation. The phrase 'without another adaptation or AI call' distinguishes it from tailoring siblings like tailor_resume and create_tailored_resume without needing to name them.

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?

There is an explicit trigger ('Use this when the user wants the same tailored resume in another Matchaa template') plus operational guidance ('Pass the latest operationId'), which also implies the negative case: do not use this when content must change. It stops short of naming the alternatives for the content-change case, but the when-to-use condition is unambiguous.

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