Skip to main content
Glama

Save time and energy

save_capacity

Record realistic hours per week and current energy (1–10) to limit how many habits can be active at once.

Instructions

Save realistic hours per week for the plan and current energy from 1 to 10. This caps how many habits can be active at once.

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": {
      "hoursPerWeek": "<hoursPerWeek>",
      "energy": "<energy>"
    },
    "name": "save_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
energyYes
hoursPerWeekYes

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?

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful side effect: the saved energy/hours constrain how many habits can be active simultaneously. It omits whether re-saving overwrites prior capacity, whether lowering the values deactivates already-active habits, and what validation failures look like.

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 with the action front-loaded and no filler; the value description precedes the behavioral consequence, which is the right ordering. Nothing is wasted, though a third clause covering overwrite semantics would have been worth the space.

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 two-parameter mutation tool with no annotations and no output schema, the description covers what is saved and one downstream effect, which is reasonable. It is still incomplete on the operation's most consequential behavior: what happens to currently active habits when the saved capacity drops below the number already running.

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 description coverage is 0%, so the description must supply meaning for both parameters. It adds real semantics for hoursPerWeek ('realistic', per week, for the plan) beyond the bare numeric bounds, but only restates the 1-10 range for energy without clarifying what the scale direction means or how it maps to the habit cap.

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 and resource pair: saving weekly hours and energy as a 'capacity' record for the plan, with concrete value domains (hours per week, energy 1-10). It does not differentiate itself from the many sibling save_* tools (save_baseline, save_plan_extras, save_goal), so an agent must infer the boundary from the resource wording alone.

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 when-to-use guidance, no prerequisite or ordering hints relative to save_plan/save_baseline, and no exclusions. The only contextual hook is the downstream effect ('caps how many habits can be active at once'), which describes consequence rather than when to call it.

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