Skip to main content
Glama

Audit a resume rewrite

audit_resume_rewrite

Use this when the user wants to check a rewritten resume against its original: compares both texts and reports which changes the original supports, which need confirmation and what was dropped, with the source lines. Does not rewrite the resume or produce a PDF. Identical retries reuse the operation.

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>",
      "originalText": "<originalText>",
      "rewrittenText": "<rewrittenText>"
    },
    "name": "audit_resume_rewrite"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestTokenYes
originalTextYes
rewrittenTextYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's 'Identical retries reuse the operation' adds genuinely new behavioral information about idempotency/deduplication. It also characterizes the response content, which helps the agent anticipate the audit findings. It omits permission or session requirements, and does not reconcile the non-read-only annotation with what is otherwise an analysis operation, leaving a small ambiguity.

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 short sentences, front-loaded with the usage condition, then the behavior, then the exclusions; no filler. The middle clause listing the report contents is slightly dense but every element is informative.

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?

The output shape is described and an output schema exists, so return-value detail is not needed, and the non-mutating exclusions are covered. However, for a three-required-parameter tool with zero schema description coverage, the missing explanation of guestToken (and of size limits on the text fields) is a real gap an agent could trip over.

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 must carry parameter meaning, yet it never mentions any parameter by name. 'Compares both texts' weakly implies originalText and rewrittenText, but guestToken — a required, pattern-constrained 40-100 character value — is completely unexplained, leaving the agent with no clue how to obtain it (a create_guest_context sibling exists but is not referenced).

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 comparison scope: check a rewritten resume against its original, and enumerates what the report contains (supported changes, changes needing confirmation, dropped content, source lines). The closing exclusions ('Does not rewrite the resume or produce a PDF') separate it from rewrite_resume_section and render_resume_template without needing their schemas.

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?

Opens with an explicit trigger condition ('Use this when the user wants to check a rewritten resume against its original') and adds two negative conditions. It stops short of naming a specific alternative tool to use instead when the user actually wants a rewrite or a PDF, so routing is implied rather than prescribed.

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