Skip to main content
Glama

propose_resume_changes

Validate and save itemized resume change suggestions and show a review card for confirmation; preserves goal context without modifying the resume or sending email.

Instructions

校验并保存逐条修改建议,显示核对卡;来自求职目标时保留 goalId,后续准备仍检查城市与排除项。不修改简历,不发送邮件。

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>"
    },
    "name": "propose_resume_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
jobIdYes
goalIdNo
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 flag it as a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds real value beyond that by clarifying the write is limited to proposed suggestions, that a review card is surfaced, and that neither the resume nor any email is touched. What it does not cover is whether suggestions persist to a draft, how they are later applied, or what happens on validation failure.

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 tight clauses, front-loaded with the action and immediately followed by the observable outcome, then the conditional goalId rule and the two exclusions. No filler, though the final negative pair could be merged with the first clause for tighter flow.

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 four-parameter, three-required mutation tool with no output schema and no schema descriptions, the definition does enough to route the agent (proposal-only, no resume write, no email, keep goalId) but not enough to invoke it correctly. The shape of `plan` and the meaning of resumeId/jobId are the critical missing pieces.

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% and three of four parameters are required, so the description carries the full burden. It only explains one parameter — goalId should be preserved when the proposal originates from a job goal — and leaves resumeId, jobId, and especially the untyped `plan` object (the core payload of "逐条修改建议") entirely undefined.

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?

The description gives a specific verb pair ("校验并保存逐条修改建议") plus a visible effect ("显示核对卡"), and explicitly negates the two nearest misreads — it does not modify the resume and does not send email — which separates it from save_resume_version/import_resume. It stops short of naming a sibling outright, so differentiation is inferred rather than stated.

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 context is implied through the conditional "来自求职目标时保留 goalId" and the two exclusions (no resume edit, no email), which tell the agent this is a pre-commit proposal step. There is no explicit instruction on when to prefer this over save_resume_version or execute_application, so the agent must infer the boundary from the negatives.

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