Skip to main content
Glama

Plan a paced day

plan_paced_day
Read-only

Builds a pain-friendly, paced daily plan (spoon theory / energy envelope) from today's energy and pain levels and the user's task list. Orders tasks, inserts rest breaks, keeps usage near 70% of capacity and moves overflow tasks to later. Use when someone with chronic pain, fibromyalgia, chronic fatigue or long COVID asks how to pace themselves, plan their day, or avoid crashing. Does not store data.

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": {
      "energy_level": "<energy_level>",
      "pain_level": "<pain_level>",
      "tasks": "<tasks>"
    },
    "name": "plan_paced_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYesTasks the user wants to do today
pain_levelYesPain today, 0 (none) to 10 (worst)
energy_levelYesEnergy today, 1 (empty) to 10 (full)
sleep_qualityNoLast night's sleep

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral content beyond that: it orders tasks, inserts rest breaks, targets ~70% of capacity, and defers overflow tasks. 'Does not store data' reinforces the read-only annotation consistently. It stops short of noting that tasks are capped at 12 or whether deferred overflow is returned or discarded.

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?

Three sentences, front-loaded with the verb and output, then the trigger conditions, then a scope boundary. Every clause carries information — the method name, the algorithm constraints, the audience, and the non-persistence note — with no filler.

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

Completeness4/5

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

For a read-only generator with no output schema, the description effectively sketches the return value (ordered tasks, inserted breaks, ~70% capacity, overflow deferred). Annotations cover safety, so nothing critical is missing. The only small gaps are how sleep_quality influences the plan and the 12-task cap, both minor for correct invocation.

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 100%, so every parameter already carries its own description and range/enum documentation. The description only implies that energy_level, pain_level and tasks drive the plan, without adding format or weighting detail beyond the schema. Baseline 3 applies when the schema is doing the heavy lifting.

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?

The description opens with a specific verb and resource — 'Builds a pain-friendly, paced daily plan' — and names the underlying method (spoon theory / energy envelope), so the agent knows exactly what the tool produces. It is clearly distinguishable from siblings like log_daily_check_in or read_pain_lesson, which record or retrieve rather than generate a plan.

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

Usage Guidelines4/5

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

Usage is explicitly scoped: 'Use when someone with chronic pain, fibromyalgia, chronic fatigue or long COVID asks how to pace themselves, plan their day, or avoid crashing.' That is a clear trigger condition with a named audience. What's missing is a negative boundary — it doesn't name a sibling alternative or say when another tool (e.g. logging a check-in, or a calm exercise) is the better choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources