Skip to main content
Glama

Save decisions and low-energy rule

save_plan_extras

Save dated decision points with fallback actions and a one-sentence low-energy rule to guide choices during a difficult fortnight.

Instructions

Save dated decision points (question + what to do if the answer is no) and the one-sentence low-energy rule for a bad fortnight.

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": "save_plan_extras"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionsNo
lowEnergyRuleNo

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 must carry the behavioral burden. It does clarify the semantics of the payload (a decision is a question plus a fallback action), which is real value, but it says nothing about whether saving replaces or appends to existing extras, whether it requires a plan to exist first, or what happens on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and enumerates the two payloads in the order they should be understood. No filler, no repetition of the title.

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?

The tool has a nested array parameter and no annotations or output schema, so the description needs to work harder than it does. Payload semantics are covered, but persistence behavior, relationship to get_plan, and validation expectations are absent.

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 description coverage is 0%, so the description has to compensate, and it does: 'ifNot' is explained as 'what to do if the answer is no' and lowEnergyRule as a 'one-sentence' rule, which constrains expected input. It does not mention the required YYYY-MM-DD date format or which fields are optional, though the schema pattern covers the former.

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 names a specific verb (save) and two concrete resources: dated decision points and the low-energy rule. An agent can tell this writes 'plan extras' rather than the baseline, goals, or milestones handled by siblings. It stops short of differentiating from an overlapping sibling like record_decision.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The phrase 'for a bad fortnight' gives a faint situational hint but is not a usage rule, leaving the agent to infer when this belongs in a plan versus record_decision.

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