Skip to main content
Glama

save_resume

Stores your current resume text so Claude can tailor it to specific job descriptions and improve application relevance.

Instructions

Save your current resume text so Claude can tailor it to job descriptions

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": {
      "resumeText": "<resumeText>"
    },
    "name": "save_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeTextYesYour full resume in plain text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. It does not say whether a repeat call overwrites the previously saved resume, whether storage persists across sessions, whether it is scoped to a user/application, or what is returned on success.

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?

One sentence, front-loaded with the action and the object, with no redundant or filler wording. The trailing rationale clause earns its place by hinting at the downstream purpose.

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 one-parameter storage tool with fully documented schema and no output schema, the core is covered. The significant remaining gap is create-versus-overwrite semantics for an obviously stateful save operation, which matters given siblings like get_resume that read the same data.

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 single parameter already documents itself as the full resume in plain text. The description adds no formatting expectations, size limits, or handling of existing text beyond what the schema states, so 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?

The description gives a specific verb and resource ('Save your current resume text'), so an agent can immediately tell it stores resume content rather than reading, analyzing, or tailoring it. It does not distinguish itself from the sibling save_profile, which an agent must infer covers a different resource.

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 only implied through the clause 'so Claude can tailor it to job descriptions', which suggests calling it before a tailoring step. There is no explicit when-to-use, no exclusion such as when to prefer save_profile, and no mention of prerequisites like having resume text already available.

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