Compass OS: Career

list wins

list_wins

Read-onlyIdempotent

List the user's wins log, newest first: the total, and the 10 newest wins with their date, what they did, the result and the role it happened in (older ones are on the Wins page). Use it to name a win for edit_win or delete_win (by date and text, as shown here) or to pick results for a resume; for a year's or a role's summary with share images use get_rewind. 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": "list_wins"
  }
}

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?

The critical behavioral disclosure is the 10-item cap and the note that older wins live on the Wins page, which tells the agent the result is truncated and prevents it from assuming a complete history. Ordering (newest first) is also disclosed. "Read-only" merely restates readOnlyHint=true, but the truncation detail is real added value.

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 return shape is front-loaded in the first sentence and the routing guidance follows, so the reader gets the essentials immediately. The second sentence is dense but every clause (edit/delete identifiers, resume results, get_rewind alternative) carries weight; only "Read-only" is redundant with 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?

With an output schema present, the description only needs to cover ordering, scope, and routing, and it does all three, including the cap that the output schema alone would not signal. Nothing an agent needs in order to call it or interpret it 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?

There are zero input parameters, so the baseline is 4. The description still adds useful meaning by noting that wins are referenced for editing or deletion "by date and text, as shown here," which clarifies how the returned fields feed into sibling tools.

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?

"List the user's wins log, newest first" gives a specific verb and resource, then enumerates exactly what comes back (total, 10 newest wins with date, action, result, role). That level of specificity makes it unmistakable next to get_rewind, which is named as the summary alternative.

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 states two concrete use cases (fetching a date/text identifier for edit_win or delete_win, and sourcing results for a resume) and explicitly redirects to get_rewind when the agent wants a year or role summary with share images. The when-not condition is spelled out rather than 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?