Compass OS: Career

get material

get_material

Read-onlyIdempotent

Read the full markdown text of the master resume (company and title left empty), or of a tracked role's saved tailored resume or cover letter (by company and title), with how many of its claims the profile doesn't back up. Read it before suggesting edits or calling edit_material; for a score and weak spots use check_resume, and for the profile itself use get_profile. Read-only. A role with nothing saved yet says to draft one with tailor_material; the master has no cover letter.

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

Input Schema

Name	Required	Description
`kind`	Yes	Which document: resume or cover_letter
`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"
+}

Changed4 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 / 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.4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/no-open-world, and the description reinforces 'Read-only' while adding real behavioral context: the empty-role response tells the caller to draft with tailor_material, and the master has no cover letter. It stops short of describing pagination or size limits for the full markdown body, which is the one remaining gap.

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-loads the primary capability, then packs routing guidance and edge cases into two dense sentences with no filler. Slightly run-on, but every clause carries information an agent needs.

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?

For a three-parameter read tool with full schema coverage, an output schema, and annotations, the description covers what is returned (markdown text plus claim count), when to use it, prerequisites, and the two edge cases (unsaved role, master cover letter). Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the enum for kind and the nullability of title/company are already documented, including 'leave empty for the master resume'. The description restates that convention (company and title left empty) rather than adding new semantics, so baseline 3 applies.

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 (read) and precise resource (master resume markdown text, or a tracked role's tailored resume/cover letter), plus an extra return detail (count of unbacked claims). It explicitly distinguishes itself from check_resume and get_profile, so an agent can pick it without opening any 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 precondition ('Read it before suggesting edits or calling edit_material') and names the alternatives with the conditions that select them ('for a score and weak spots use check_resume, and for the profile itself use get_profile'). It also routes the empty-role case to tailor_material.

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?