Skip to main content
Glama

Change today

morning_check_in
Destructive

Each day is planned on its own each morning. When the athlete's day is different, this tells the coach how many minutes they have today and what they cannot do, and the coach plans today's sessions again around it. Returns them. Takes up to a minute.

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": {
      "minutes": "<minutes>"
    },
    "name": "morning_check_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayNoThe person's local date as YYYY-MM-DD, the day before if it is earlier than 05:00 where they are. Omit if unknown.
minutesYesMinutes they have for training today.
cannot_doNoWhat they cannot do today, e.g. swimming when there is no pool. Omit if everything is possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description is consistent, explaining that today's sessions are planned 'again' around the new constraints, so existing plans are regenerated. It also adds information annotations do not carry: the call 'Takes up to a minute', and that it returns the re-planned sessions. It omits whether the change is reversible or requires an existing plan.

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 sentences with the trigger stated first and useful facts (latency, return) appended. The fragment 'Returns them' has an unclear antecedent, which is a small structural flaw but not bloat.

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 mutation tool with full schema coverage and annotations covering the safety profile, the description covers the trigger, the replanning effect, latency and a vague return note. With no output schema, 'Returns them' is too thin to tell the agent what comes back, and nothing is said about permissions or preconditions.

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 the schema already documents minutes, cannot_do and the date handling (including the before-05:00 rule). The description only restates minutes and cannot_do in prose and says nothing about the optional 'today' parameter, so the baseline 3 applies.

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 conveys a specific effect: given today's available minutes and what the athlete cannot do, today's sessions are re-planned. The verb is indirect ('this tells the coach... the coach plans...'), but an agent can identify the resource (today's plan) and the outcome. It does not explicitly separate itself from edit_schedule or today, which keeps it out of 5 territory.

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?

It states a clear trigger condition — 'When the athlete's day is different' — which tells the agent when this tool applies rather than a manual schedule edit. It names no alternatives (edit_schedule, schedule) and gives no exclusions, so it stops short of 5.

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