Skip to main content
Glama

Undo a change

restore_version
DestructiveIdempotent

Use this when the person asks to undo a change CVEmber made. Puts the resume back to how it was before the latest change, or the one named by actionId.

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": {
      "resumeId": "<resumeId>"
    },
    "name": "restore_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionIdNoAn action id from get_resume's history; the latest if omitted.
resumeIdYesA resume id from list_resumes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is largely covered. The description adds the useful nuance that this is a revert-to-prior-state rather than a deletion, and that the target defaults to the latest change. However, it never says whether changes made after the chosen actionId are lost, or whether the undo itself can be reversed, which is exactly the risk an agent needs surfaced for a destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first front-loads the invocation trigger, the second states the effect and the optional targeting. No filler, no restatement of the tool name, and every clause carries information.

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 tool is simple (2 params, 1 required, no output schema) and richly annotated, so most of the burden is met. The remaining gap is the destructive consequence: restoring to an earlier actionId presumably discards later changes, but the description never confirms or bounds that, leaving the agent to guess at blast radius. Adequate but not complete for a destructive mutation.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already explains both resumeId ('A resume id from list_resumes') and actionId ('An action id from get_resume's history; the latest if omitted'). The description only restates the default-to-latest behavior, adding no format, validation, or failure semantics beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb-plus-resource framing: reverts a resume to its state before a given change, either the latest one or the one named by actionId. An agent can distinguish this from update_resume or tailor_resume because it speaks of undoing a prior CVEmber action rather than applying a new one. It stops short of 5 because it never names the sibling it should be preferred over.

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?

Gives an explicit trigger: 'when the person asks to undo a change CVEmber made.' That is a clear when-to-use condition tied to user intent. There is no when-not guidance and no stated alternative (e.g., using update_resume to correct a change instead of reverting it), so it falls short of the 5 bar.

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