Skip to main content
Glama

save_resume_version

Saves user-approved resume edits for a specific job, creating a tailored copy and new PDF while preserving the original resume.

Instructions

校验宿主给出的建议,仅应用用户选择的 sectionId:lineIndex,保存岗位副本和新 PDF。原 PDF 保留;当前新 PDF 为简洁文本排版,不保留原布局及照片。

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>",
      "jobId": "<jobId>",
      "plan": "<plan>",
      "accepted": "<accepted>"
    },
    "name": "save_resume_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
jobIdYes
acceptedYes
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds genuinely non-obvious behavior: the original PDF is preserved, and the new PDF is plain-text layout that drops the original formatting and photos. It omits what happens when validation fails and whether the saved copy is retrievable.

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?

Two sentences, front-loaded with the validate-then-apply action, followed by the PDF retention caveat. No redundant restatement of the name. Dense but 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?

For a mutation tool with four undocumented required parameters and no output schema, the description covers the key side effects but leaves the parameter contract and the failure/validation path unstated. The PDF-format caveat is the most valuable piece and it is present, so it is adequate rather than complete.

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 four required parameters, so the description must compensate and largely does not. It does explain the format of entries in 'accepted' as sectionId:lineIndex, which is useful, but 'plan', 'jobId', and 'resumeId' are left completely unexplained in both schema and description.

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?

States specific actions: validate the host's suggestions, apply only the user-selected sectionId:lineIndex entries, and save the job copy plus a new PDF. The verb+resource combination (save_resume_version) is made concrete, and the 'only apply user-selected' clause implicitly separates it from propose_resume_changes. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'only apply what the user selected' tells the agent this is the commit step after suggestions have been proposed and chosen. There is no explicit when-to-use/when-not framing and no named alternative, so an agent must infer the sequencing from the sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.