Skip to main content
Glama

Save a goal

save_goal

Create or update a chosen values-based goal with a specific statement, identity, and WOOP plan, keeping active goals limited to three.

Instructions

Create or update one goal (max 3 active). Only after the person chose it. Include the value it serves, a specific statement (what, how much, by when), an identity statement and the WOOP answers.

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": {
      "area": "<area>",
      "value": "<value>",
      "statement": "<statement>"
    },
    "name": "save_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPass to update an existing goal
areaYes
woopNo
valueYes
statusNo
identityNo
statementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose two behavioral traits: the 3-active limit and the ordering requirement that the person must have already chosen the goal. It omits what happens at the cap (reject? evict?), whether passing id merges or replaces, and what the status lifecycle (active/done/dropped) means.

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?

Three short, front-loaded sentences: the action and the cap come first, then the precondition, then required content. The only weakness is telegraphic jargon like "the WOOP answers" and "identity statement" that a fresh agent may not parse.

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 7-parameter, nested-object mutation tool with no annotations and no output schema, the description covers the shape of the write but not the semantics of area, status, or cap-exceeded behavior. Adequate, not complete.

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 only 14%, so the description must compensate. It does add real meaning for value, statement (what, how much, by when), identity and the WOOP object, but the required area parameter is unexplained in both schema and description, and the status enum is never mentioned.

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?

The description states a specific verb pair (create or update) and resource (one goal), plus a hard constraint (max 3 active) that no sibling name implies. It stops short of differentiating itself from the other save_* tools, but an agent can tell what this tool produces.

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

Usage Guidelines3/5

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

"Only after the person chose it" is a genuine precondition and the max-3-active cap is a real usage boundary. However, there is no guidance on what to do when the cap is hit, no alternative tool named, and no distinction from save_habit/save_values despite near-identical verbs.

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