Compass OS: Career

list pipeline

list_pipeline

Read-onlyIdempotent

List every role the user tracks in their Compass OS pipeline: company, title, location, stage, fit percentage (once the pipeline page has scored it) and a link to its card. Use it to check whether a role is already tracked, to pick roles by place or stage, or to get the exact titles move_job, remove_jobs and the other role tools take; for one role's posting and fit use get_job, and for untracked scan results use find_jobs. Read-only: a blank location is filled in from the role's posting page for this answer only, not saved.

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

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

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds a non-obvious behavioral detail: a blank location is filled from the role's posting page for this answer only and is not saved. It does not discuss volume or ordering, but the transient enrichment disclosure is the key extra context.

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?

It is front-loaded with the returned fields, then moves through use cases, sibling alternatives, and the read-only caveat. The sentence is dense but every clause carries routing or behavioral value; a bulleted layout could read faster, 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?

An output schema already describes the return shape and the annotations cover safety semantics. The description supplies the remaining necessary context: what is listed, when to use it, which siblings to use instead, and the transient location-fill behavior. Nothing an agent needs 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 has zero parameters and an empty schema at 100% coverage, so the baseline is 4. The description correctly avoids inventing parameter guidance and instead focuses on scope and routing.

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?

The description uses a specific verb and resource ('List every role the user tracks in their Compass OS pipeline') and enumerates the returned fields: company, title, location, stage, fit percentage, and card link. It also explicitly distinguishes itself from get_job and find_jobs, so an agent can identify its scope without inspecting 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?

It gives concrete when-to-use cases: checking whether a role is already tracked, filtering by place or stage, and obtaining exact titles required by move_job and remove_jobs. It also routes the agent away to get_job for a single posting and fit, and to find_jobs for untracked scan results.

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?