Compass OS: Career

list inbox

list_inbox

Read-onlyIdempotent

List recruiter mail Compass OS couldn't match to a tracked role yet (sender, subject and kind), and the user's upcoming interviews by company, title and time. Use it for "any recruiter mail?" or "when's my next interview?"; for the stages of tracked roles use list_pipeline. Read-only: it doesn't sort, answer or archive mail. Items from Gmail or Calendar show only in the card; the text gives just their count.

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_inbox"
  }
}

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?

Beyond the readOnlyHint/idempotentHint annotations it adds real behavioral facts: it does not sort, answer or archive mail, and Gmail/Calendar items surface only in the card while the text yields just a count. The one partly redundant element is restating read-only, and it says nothing about result volume or limits, so it is strong but not fully exhaustive.

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?

Scope comes first, then usage triggers, then exclusion and behavioral caveats — a sensible front-loaded order with no filler. The opening sentence is long and stacks two resources plus parenthetical field lists, which costs some immediate readability but every clause carries information.

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 zero-parameter read tool with an output schema already documenting return shape, the description covers everything an agent needs: what it returns, when to call it, which sibling to use instead, and the card-versus-text rendering caveat. No material gap remains.

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 schema has zero parameters, so the baseline is 4 and there is no parameter semantics for the description to compensate for. The description correctly requires no caller inputs and frames the tool as a parameterless inbox snapshot.

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 names a specific verb (list) and two concrete resources (unmatched recruiter mail, upcoming interviews), and states the fields returned for each (sender/subject/kind; company/title/time). It explicitly distinguishes itself from list_pipeline by scope, so an agent can choose between them without opening either 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 direct user-utterance triggers ("any recruiter mail?", "when's my next interview?") plus an explicit routing rule away from this tool ("for the stages of tracked roles use list_pipeline"). Both the use case and the boundary against the nearest sibling are stated, not implied.

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?