Skip to main content
Glama

duplicate_resume

Copy one resume to a new id, such as a tailored copy for one posting. The source is not changed. To change an existing resume, use update_resume. Returns the new resume, its version, and an appUrl.

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": {
      "fromResumeId": "<fromResumeId>"
    },
    "name": "duplicate_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
fromResumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is largely covered. The description still adds genuine value by reassuring that the source resume is untouched, which is the main risk question for a copy operation. It also discloses the return payload (new resume, version, appUrl), filling the gap left by having no output schema.

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?

Three short sentences, front-loaded with the action and scenario, then the source-preservation constraint, then the alternative routing and return value. No sentence is redundant.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter copy tool with annotations covering safety, the description covers action, side effect, alternative, and return shape, which is most of what an agent needs. The remaining gap is the semantics of the optional title parameter and whether version history carries 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 and it only partially does. "fromResumeId" is implicitly the source being copied, but the "new id" mentioned is server-generated and not a parameter, and the optional "title" parameter is never explained (e.g. whether it defaults to the source title).

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?

"Copy one resume to a new id" states a specific verb and resource, and the tailored-copy example pins down the intended scenario. The sentence "To change an existing resume, use update_resume" separates it from the closest sibling without opening either 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?

The description gives a positive use case (a tailored copy for one posting) and an explicit exclusion naming the alternative tool for in-place modification. An agent has both the when and the when-not stated outright.

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