Compass OS: Career

check resume

check_resume

Read-onlyIdempotent

Run Resume Studio's check on the master resume (company and title left empty) or a tracked role's tailored resume (by company and title): the score out of 100 with its parts, failing checks, the weakest bullets with their issue, and, for a role, the posting's keywords it has and misses. Use it before edit_resume, so you can name the problem; for the resume's full text use get_material, and for gaps in the profile use get_profile. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_resume"
  }
}

Input Schema

Name	Required	Description	Default
`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.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint and closed-world, so the trailing 'Read-only' is redundant. The value-add is the disclosure of what the check actually reports (scoring parts, failing checks, per-bullet issues, matched/missing keywords), which tells the agent what evidence it will get back before deciding to call it.

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?

Two sentences, front-loaded with the primary action and immediately followed by routing guidance. Dense but every clause carries information; the only wasted words are the closing 'Read-only' that repeats the annotations.

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 an optional-parameter read tool with full schema coverage and an output schema, nothing needed to call it correctly is missing: mode selection is unambiguous, expected output is signposted, and sibling routing is handled.

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% and already states that both fields should be left empty for the master resume, so the description's restatement of that rule adds little beyond confirming the pairing semantics (company+title together select a tracked role). No format or matching-behavior detail (e.g. exact-string vs fuzzy title matching) is added, so the baseline 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 and resource (run the check on either the master resume or a tracked role's tailored resume) and enumerates the returned artifacts: score out of 100, its parts, failing checks, weakest bullets, keyword coverage. An agent can distinguish this from edit_resume or get_material 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit sequencing rule ('Use it before edit_resume, so you can name the problem') and names two alternatives with their distinct purposes (get_material for full text, get_profile for profile gaps). Minor gap: it doesn't warn about when the check is not meaningful (e.g. a role with no posting).

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?