Skip to main content
Glama

Inspect the resume image

inspect_resume
Read-only

Use this when you need to look at the current revision yourself before finalizing: returns the PNG pixels and the previewReceipt directly, without a card or a user click. Actually examine the image. If your client cannot read the pixels, use preview_resume instead. Same ownership and rendering checks. No AI call.

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

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this read-only, non-destructive, and closed-world, so the description is not required to re-establish safety. It still adds real behavioral context beyond them: no card or user interaction, no AI call, and that the same ownership and rendering checks apply as the preview path. It stops short of stating cost, latency, or size limits for the pixel payload.

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?

The usage condition and the sibling alternative are front-loaded in the first two sentences, and the closing 'No AI call' is an efficient qualifier. Some sentences are telegraphic ('Actually examine the image.'), but nothing is padding.

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?

Return values are described well enough given there is no output schema, and the read-only nature is covered by annotations. However, a tool requiring two opaque required tokens with zero schema documentation leaves an agent without the information needed to construct a valid call, which is a material gap.

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 completely undocumented in the schema. The description never explains what these identifiers are, where they come from, or how ownership is scoped through guestToken, so it fails to compensate for the coverage 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?

The description states a concrete verb and resource — it returns 'the PNG pixels and the previewReceipt' for the current revision — and immediately distinguishes itself from the sibling preview_resume by noting the absence of a card or user click. An agent can tell exactly what it gets back without opening the 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?

It names the triggering condition ('when you need to look at the current revision yourself before finalizing') and the exclusion condition with a named alternative ('If your client cannot read the pixels, use preview_resume instead'). Both the when and the when-not are explicit.

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