Skip to main content
Glama

readiness_history

Read-only

Retrieve per-morning readiness estimates with their main inputs and Garmin readiness scores to compare model tracking against Garmin; set days and an optional end date.

Instructions

Per-morning readiness estimate (at wake) next to its main inputs and any Garmin readiness scores logged, to judge how well the model tracks Garmin.

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

Input Schema

NameRequiredDescriptionDefault
endNo
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context the annotations do not: the row grain is one estimate per morning at wake, rows are aligned with their model inputs and any externally logged Garmin scores, enabling comparison. It does not mention default window behavior (days=21) or what happens when no Garmin score exists for a morning.

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?

A single dense sentence with no filler, leading with the resource grain before the comparative purpose. The phrase 'next to its main inputs' is slightly awkward but does real work by describing row alignment.

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?

An output schema exists, so return-value detail is not required, and annotations cover the safety profile. For a history/range tool, though, the missing window semantics (default 21 days, valid range, date format for 'end') and the absent pointer to log_garmin_readiness as the counterpart leave the agent guessing on invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters (end, days), and the description supplies no interpretation of either — not the default 21-day window, not whether 'end' is a date string bound or inclusive/exclusive, not the expected format. With 2 undocumented params the description is the only channel available and it says nothing.

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 the specific resource (per-morning readiness estimate at wake) and what accompanies it (model inputs and logged Garmin readiness scores), making it distinguishable from the write sibling log_garmin_readiness. It never uses an explicit verb like 'returns' or 'lists', so the action is inferred from the noun phrase rather than stated.

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?

The stated purpose — 'to judge how well the model tracks Garmin' — implies model-validation usage, but there is no explicit guidance on when to pick this over daily, morning_check, hrv_night, or the write-side log_garmin_readiness. The agent must infer that this is the read/history counterpart rather than being told.

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