Skip to main content
Glama

Finalize and deliver the PDF

finalize_resume
Idempotent

Use this when a reviewed revision is ready to deliver: requires the fresh previewReceipt of this exact revision and previewReviewed=true after you actually examined its image or PDF. Refuses a missing, expired or other revision's preview, overflowing text, or a PDF missing the name, summary, experience or education titles. These checks do not prove that facts are true. Freezes the revision, without another adaptation, and returns its private PDF link.

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>",
      "contentReviewed": "<contentReviewed>",
      "reviewNote": "<reviewNote>"
    },
    "name": "finalize_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
reviewNoteYes
operationIdYes
previewReceiptNo
contentReviewedYes
previewReviewedNo

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real substance on top: validation gates, refusal conditions, and the "freezes the revision, without another adaptation" consequence. However, it is silent on how the idempotency hint plays out in practice (e.g. whether a second call with the same receipt returns the same link or errors) and says nothing about the guestToken/auth path. Useful, but not the full behavioral picture for a mutating delivery tool.

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 tight sentences, front-loaded with the trigger and then the failure modes, with no filler. The parenthetical "These checks do not prove that facts are true" earns its place as a scope disclaimer. The middle sentence is dense enough that a reader has to parse it twice.

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 description still notes the private PDF link. With no annotations covering inputs and 0% schema description coverage across six parameters, though, the description should also say what guestToken identifies and what purpose reviewNote serves. What is present is high quality; what is absent is half the input surface.

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

Parameters4/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; it delivers for the two parameters that matter most, spelling out that previewReceipt must be fresh and belong to this exact revision and that previewReviewed must be true only after real inspection. However, guestToken, operationId, reviewNote, and contentReviewed get no explanation at all, and an expired receipt is mentioned without saying when that happens. Partial but meaningful compensation for a 6-parameter, undescribed schema.

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 outcome: it freezes the revision and returns its private PDF link, and the title/description pair together pin down exactly which resource is being delivered. An agent can distinguish this delivery step from preview_resume or get_resume_document without opening any 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?

Explicitly names the trigger condition ("when a reviewed revision is ready to deliver") and the prerequisite state (fresh previewReceipt for this exact revision plus previewReviewed=true after actually examining the image or PDF). It also enumerates the cases where the call must not succeed, which is stronger guidance than a simple when-to-use note.

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