Compass OS: Career

edit material

edit_material

DestructiveIdempotent

Save the user's own changes to the master resume (company and title left empty) or a tracked role's tailored resume or cover letter: the whole document in markdown in text (read it with get_material, then change only what they asked), or one line by giving its current text in line and its new wording in text. Use edit_resume for Resume Studio's AI edits, and tailor_material for a fresh draft. Use only facts from the profile; every claim is checked again and unbacked ones are counted in the reply. It asks the user first and replaces the saved document. 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": {
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "edit_material"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Which document: resume or cover_letter
`line`	No	To change one line only: its current text, as get_material shows it
`text`	Yes	The whole new document in markdown; with line, just that line's new wording
`title`	No	The tracked role's title as the pipeline lists it; leave empty for the master resume
`company`	No	The tracked role's company; leave empty for the master resume

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 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 / company / description

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

addedInput schema / properties / kind / description

Added value: +"Which document: resume or cover_letter"

addedInput schema / properties / line / description

Added value: +"To change one line only: its current text, as get_material shows it"

addedInput schema / properties / text / description

Added value: +"The whole new document in markdown; with line, just that line's new wording"

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.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds context beyond them: it asks the user before replacing the saved document, every claim is re-checked against the profile and unbacked ones are counted in the reply, the reply contains the changed lines, and undo can restore the document within 24 hours.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded, but the first sentence is a dense run-on that packs mode selection, prerequisites and file scope together. 'Returns the changed lines' partly duplicates the output schema, so not every clause earns its place.

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 destructive, confirmed write with an output schema and full parameter coverage, the description covers the confirmation prompt, the replacement behavior, the undo window and the fact-checking constraint. Only the exact output shape is left to the output schema, which is appropriate.

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 explains the two editing modes: supplying text alone means the whole markdown document, whereas supplying line plus text changes a single line whose current text must match what get_material shows. That clarifies how the parameters interact in a way the schema descriptions only partially convey.

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: saving the user's own changes to the master resume (company/title empty) or a tracked role's tailored resume or cover letter. It explicitly contrasts itself with edit_resume (AI edits) and tailor_material (fresh draft), so an agent can distinguish it from siblings without opening schemas.

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 explicit when-to-use and when-not-to-use: use edit_resume for Resume Studio's AI edits, tailor_material for a fresh draft, and read the document with get_material first before changing only what was asked. Alternatives and the prerequisite step are named directly.

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?