Skip to main content
Glama

Reword a resume section

rewrite_resume_section
Idempotent

Use this when the user asks to reword or shorten the summary, or to reword one experience bullet: uses the Matchaa website's targeted rewriting from the latest revision and creates a new revision, keeping facts and qualifiers. userRequest quotes the user's request. Review the result. For wording the user supplied, use update_resume.

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>",
      "path": "<path>",
      "mode": "<mode>",
      "userRequest": "<userRequest>"
    },
    "name": "rewrite_resume_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
pathYes
guestTokenYes
operationIdYes
userRequestYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotent=true), and the description adds real context beyond them: the operation reads the latest revision, creates a new revision rather than overwriting in place, and preserves facts and qualifiers. It does not mention the guest-token auth requirement or how operationId is used to track the operation, which is a notable omission for a write 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?

It is front-loaded with the trigger condition and uses a small number of tight sentences with no filler. The mid-sentence aside about the Matchaa website and the trailing "Review the result" are slightly awkward in placement but not wasteful.

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

Completeness2/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, but the definition leaves four of five required parameters undefined and never says what operationId is for, even though a get_operation sibling exists. For a mutation tool with guest-token auth and a revision model, this is under-specified.

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% across five required parameters, so the description must carry the load — but it only explains userRequest ("quotes the user's request"). path, mode, guestToken, and operationId are left to their enum/pattern constraints, with no prose on the allowed path shapes (summary vs. experiences.N.bullets.N) or on why an operationId is required.

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 names a specific action and resource: reword or shorten the summary, or reword a single experience bullet. It also states the mechanics — targeted rewriting from the latest revision that produces a new revision while keeping facts and qualifiers — which is enough for an agent to distinguish it from update_resume.

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 opens with an explicit trigger ("Use this when the user asks to reword or shorten...") and names the alternative with the condition that selects it ("For wording the user supplied, use update_resume"). It also tells the agent to review the result before accepting it.

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