Skip to main content
Glama

Log a win

add_win

Record a completed action and the change it created so Life Compass can use those wins for reviews, confidence, and career promotion cases.

Instructions

Note something the person did and what changed because of it. Wins feed reviews, confidence and, for career goals, promotion cases.

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": {
      "text": "<text>"
    },
    "name": "add_win"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose downstream effects (feeds reviews, confidence, promotion cases), which is genuine behavioral context an agent could not get from the schema. However, it never states that this is a write operation with persistence, whether duplicates are merged, or what comes back on success.

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?

Two short sentences: the definition leads and the rationale follows, with no padding or repetition. Nothing is wasted, though the second sentence is motivation rather than operational detail, so it earns slightly less than a purely actionable line would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter logging tool with no output schema, the description covers what to record and why it matters, which is close to sufficient. The remaining gap is the unexplained `tag` field and the absence of any statement about what happens after the record is saved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It does define the content of the required `text` parameter well by tying the writing to an action plus its resulting change. The optional `tag` parameter gets no mention at all, leaving half the surface undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Note something the person did and what changed because of it" gives a specific verb (note/record) plus the exact shape of the resource: an action paired with its outcome. It is far more than a restatement of "add_win." It stops short of naming any sibling (e.g. save_reflection, record_decision), so the boundary with adjacent logging tools is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains why wins matter (reviews, confidence, promotion cases) but never says when to use this tool rather than save_reflection or record_decision, nor when not to. There is no prerequisite, timing, or exclusion guidance; the agent must infer the trigger condition from the word "win" alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.