Compass OS: Career

get career timeline

get_career_timeline

Read-onlyIdempotent

Show the user's career as a timeline: every employer in the profile, newest first, with dates and how many wins are logged there. Roles in a row at one company form one stint, each step named (a promotion or a role change) and marked when it's only suggested; the profile's schools follow. It comes with a share image to download. Use it for "show my career"; for a summary of wins over a period use get_rewind, and to confirm a suggested step use link_roles. Read-only: nothing is saved or shared.

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": "get_career_timeline"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, and the description restates the read-only nature rather than adding to it. It does add real behavioral context beyond the annotations: the result includes a downloadable share image and flags steps that are only suggested rather than confirmed. It stops short of saying whether the share image is generated fresh each call or reused.

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?

The content is front-loaded (what it shows, then how stints are structured, then routing guidance) and no sentence is filler. The share-image detail arrives mid-stream and briefly interrupts the output description, a minor structural blemish in an otherwise tight passage.

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?

With no parameters, an output schema present, and annotations covering safety, the description's job is mainly to convey scope and shape, which it does thoroughly. Minor gaps remain around the share image and the ordering of schools, but 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?

The tool takes zero parameters, so the baseline applies and there is nothing for the description to disambiguate. No misleading parameter claims are made.

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 ("Show the user's career as a timeline") and then enumerates the content: employers newest first, dates, win counts, stints with named steps, suggested-step markers, schools, and a share image. An agent can distinguish this from get_rewind or link_roles 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 selection cue ("Use it for 'show my career'") and names two alternatives with the conditions that select them: get_rewind for a period summary of wins, link_roles to confirm a suggested step. Both when-to-use and when-to-use-something-else are covered.

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?