Skip to main content
Glama

Preview the resume

preview_resume
Read-only

Use this when you need to show or check the current revision and your client cannot read the images returned by inspect_resume: returns the exact PNG through a card, layout warnings and a private PDF link. Returns the previewReceipt required by finalize_resume; any change needs a new preview. No AI call. If the image cannot be used, say so and do not claim a visual review.

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": "preview_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
operationIdYes

Output Schema

NameRequiredDescriptionDefault
layoutYes
downloadUrlNo
operationIdYes
previewReceiptNo
reviewRequiredYes
contentWarningsYes
expiresInSecondsNo
previewExpiresInSecondsNo

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?

Annotations already declare readOnly/non-destructive/closed-world, and the description goes well beyond them: no AI call is made, the output includes layout warnings and a private PDF link, a receipt is produced that finalize_resume consumes, and staleness rules apply. It even cautions the agent not to claim a visual review if the image fails — a behavioral constraint no annotation could express.

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?

Front-loaded usage condition followed by return contents, dependency, and a fallback caveat; every sentence carries actionable information. It is slightly dense and packs four distinct concerns into one paragraph, but there is no filler.

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?

Output schema exists, so return values need not be re-explained, yet the description helpfully summarizes them and adds the receipt/staleness semantics. The remaining hole is input: two required parameters with no explanation anywhere. For a read-only preview tool that is the one substantive incompleteness.

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% for two required parameters (guestToken, operationId), so the description carries the full burden of explaining them — and it says nothing about either. The only identifier-adjacent information is the return-side previewReceipt, which is not a parameter. With zero coverage and no compensating explanation, this is a clear gap.

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 (preview/show) and resource (current resume revision) and enumerates exactly what comes back: the exact PNG via a card, layout warnings, and a private PDF link. It also explicitly positions itself against inspect_resume, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this when the client cannot read the images returned by inspect_resume. It also states the downstream contract (the previewReceipt is required by finalize_resume, and any change needs a new preview) and a fallback instruction when the image is unusable. That is when-to-use, prerequisite, and exclusion all in one.

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