Compass OS: Career

edit resume

edit_resume

Destructive

Make one of Resume Studio's AI edits to the master resume (company and title left empty) or a tracked role's resume (by company and title), and save the result: fix (every open suggestion at once), shorten, add_keywords (the given keywords, or the posting's ones the background supports), or improve_bullet (rewrite the given bullet). Call check_resume first; to save the user's own wording use edit_material, and for a fresh tailored draft use tailor_material. It asks the user first, uses their AI, replaces the saved resume (the master's previous version is kept), and checks every claim against the profile. Returns the changed lines. Once it's saved, undo can put it back within 24 hours.

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": {
      "action": "<action>"
    },
    "name": "edit_resume"
  }
}

Input Schema

Name	Required	Description
`title`	No	The tracked role's title as the pipeline lists it; leave empty for the master resume
`action`	Yes	The edit: fix, shorten, add_keywords or improve_bullet
`bullet`	No	For improve_bullet: the bullet to rewrite, quoted as check_resume shows it
`company`	No	The tracked role's company; leave empty for the master resume
`keywords`	No	For add_keywords: the keywords to work in; leave empty for the posting's ones the profile supports

Output Schema

Name	Required	Description
`text`	Yes	The answer, or what was done, in plain words for the user: the same text as content
`undo`	No	On a saved write: its undo handle, for undo within 24 hours
`widget`	No	The card the host draws with it, e.g. "pipeline"; "confirm" means a write waits for the user's Yes and nothing is saved yet

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / bullet / description

Previous value: -"For improve_bullet: the bullet to rewrite, quoted as resume_check shows it"New value: +"For improve_bullet: the bullet to rewrite, quoted as check_resume shows it"

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / undo

Added value: +{
+  "description": "On a saved write: its undo handle, for undo within 24 hours",
+  "type": "string"
+}

Changed6 schema fields changedNov 4, 2026

addedInput schema / properties / action / description

Added value: +"The edit: fix, shorten, add_keywords or improve_bullet"

addedInput schema / properties / bullet / description

Added value: +"For improve_bullet: the bullet to rewrite, quoted as resume_check shows it"

addedInput schema / properties / company / description

Added value: +"The tracked role's company; leave empty for the master resume"

addedInput schema / properties / keywords / description

Added value: +"For add_keywords: the keywords to work in; leave empty for the posting's ones the profile supports"

addedInput schema / properties / title / description

Added value: +"The tracked role's title as the pipeline lists it; leave empty for the master resume"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "text": {
+      "description": "The answer, or what was done, in plain words for the user: the same text as content",
+      "type": "string"
+    },
+    "widget": {
+      "description": "The card the host draws with it, e.g. \"pipeline\"; \"confirm\" means a write waits for the user's Yes and nothing is saved yet",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description substantiates that with real consequences: it asks the user first, uses their AI, replaces the saved resume, keeps the master's previous version, and offers undo within 24 hours. It also discloses validation behavior ("checks every claim against the profile") and the return payload ("Returns the changed lines") — meaningful context beyond the annotation flags.

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?

Front-loaded with the core action and tightly packed — every clause carries information (targets, actions, prerequisites, alternatives, side effects, undo window). The single dense paragraph with stacked parentheticals makes it harder to scan than a short bulleted structure would, but there is no filler.

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

Completeness5/5

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

Despite being a destructive, multi-mode mutation, the definition covers prerequisite ordering, target selection, action semantics, user confirmation, version retention, claim validation, and reversibility. An output schema exists, and the description still summarizes the return value briefly, so nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: fix means "every open suggestion at once," add_keywords defaults to the posting's supported keywords when the list is empty, and improve_bullet rewrites the supplied bullet. It also clarifies the empty company/title convention for the master resume, which goes slightly beyond the schema's own wording.

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?

States a specific verb and resource ("Make one of Resume Studio's AI edits to the master resume ... or a tracked role's resume") and enumerates the four concrete edits: fix, shorten, add_keywords, improve_bullet. It also distinguishes the two targeting modes (empty company/title = master; populated = tracked role), so an agent can tell exactly what the tool does without opening the 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?

Gives an explicit prerequisite ("Call check_resume first") and names both alternatives with the condition that selects each: edit_material for the user's own wording, tailor_material for a fresh tailored draft. This is the when/when-not/alternative pattern done properly.

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

All Compass OS: Career tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?