Compass OS: Career

edit win

edit_win

DestructiveIdempotent

Change one logged win: its text, result, date, or the role it happened in (company and title from get_profile). Name the win by its date and its text, as list_wins shows them, and put only what changes in set. Use delete_win to remove a win and log_win to add one. It asks the user first and changes only that win. When the text doesn't match, the reply lists that day's wins instead. Returns the changed win. Once it's saved, undo can put it back within 24 hours.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "what": "<what>",
      "set": "<set>"
    },
    "name": "edit_win"
  }
}

Input Schema

Name	Required	Description
`set`	Yes	Only the fields that change; leave the rest empty
`date`	Yes	The win's date as list_wins shows it, YYYY-MM-DD
`what`	Yes	The win's text as list_wins shows it; its first 8 or more characters are enough

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.

Changed4 schema fields changedNov 9, 2026

changedInput schema / properties / date / description

Previous value: -"The win's date as the wins tool shows it, YYYY-MM-DD"New value: +"The win's date as list_wins shows it, YYYY-MM-DD"

changedInput schema / properties / set / properties / company / description

Previous value: -"The new role. The company of the role it happened in, as profile_gaps shows it"New value: +"The new role. The company of the role it happened in, as get_profile shows it"

changedInput schema / properties / set / properties / title / description

Previous value: -"The new role. The title of the role it happened in, as profile_gaps shows it"New value: +"The new role. The title of the role it happened in, as get_profile shows it"

changedInput schema / properties / what / description

Previous value: -"The win's text as the wins tool shows it; its first 8 or more characters are enough"New value: +"The win's text as list_wins shows it; its first 8 or more characters are enough"

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / undo

Added value: +{
+  "description": "On a saved write: its undo handle, for undo within 24 hours",
+  "type": "string"
+}

Changed9 schema fields changedNov 4, 2026

addedInput schema / properties / date / description

Added value: +"The win's date as the wins tool shows it, YYYY-MM-DD"

addedInput schema / properties / set / description

Added value: +"Only the fields that change; leave the rest empty"

addedInput schema / properties / set / properties / company / description

Added value: +"The new role. The company of the role it happened in, as profile_gaps shows it"

addedInput schema / properties / set / properties / date / description
```
Added value: +"The new date. When it happened, as YYYY-MM-DD"
```

addedInput schema / properties / set / properties / result / description

Added value: +"The new result. What came of it, ideally with a number, e.g. \"cut onboarding time 30%\""

addedInput schema / properties / set / properties / title / description

Added value: +"The new role. The title of the role it happened in, as profile_gaps shows it"

addedInput schema / properties / set / properties / what / description
```
Added value: +"The new text. What the user did, in their words"
```

addedInput schema / properties / what / description

Added value: +"The win's text as the wins tool shows it; its first 8 or more characters are enough"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "text": {
+      "description": "The answer, or what was done, in plain words for the user: the same text as content",
+      "type": "string"
+    },
+    "widget": {
+      "description": "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",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The annotations only declare destructive/idempotent/write flags; the description goes well beyond them by disclosing the confirmation prompt, the single-record blast radius, the reversible 24-hour undo window, and the failure path (a non-matching text returns that day's wins instead of erroring). No contradiction with destructiveHint=true, since the described undo limits but does not deny destructiveness.

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?

Front-loaded with verb and resource, and most sentences carry operational facts (alternatives, targeting, confirmation, fallback, undo). "Returns the changed win" is slightly redundant given an output schema exists, keeping it from a 5.

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 nested-payload mutation tool with three required parameters, the description covers targeting, partial-update semantics, confirmation behavior, fallback on mismatch, sibling routing, and reversibility. With an output schema present, it need not describe the return payload further.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns extra by clarifying the non-obvious split between the top-level date/what used as an identifier and the nested set payload that carries only changed values, resolving the ambiguity of two fields both named "what".

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?

"Change one logged win: its text, result, date, or the role it happened in" gives a specific verb, a bounded resource, and enumerates the mutable fields, and the scope (one win) separates it from list_wins/log_wins without needing a schema comparison.

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 names the exact alternatives and the condition that selects them: delete_win to remove, log_win to add. It also tells the agent how to target the record (by date plus text as list_wins shows them), which is the practical prerequisite for calling this tool correctly.

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?