Skip to main content
Glama
Sign In

Blocks

by zone.blocks
OverviewDiscussionsAdmin

log_readiness

Record the athlete's daily readiness — one entry per date, idempotent MERGE-upsert: only the fields you send are updated, existing fields survive. Accepts a BATCH (up to 90 items) so you can backfill history from an export (e.g. months of HRV/RHR/sleep) in a few calls. Subjective core (McLean 1-5, 5=best: fatigue, sleep_quality, soreness, stress, mood) + prs (0-10) is the primary signal; objective fields (rhr bpm, hrv_rmssd ms, sleep_total_min, deep_sleep_min) are optional manual values from the athlete's wearable. Confounder flags (late_meal, alcohol, hookah, smoking, life_stress, illness, injury, poor_sleep_external, small_child, travel, underfuelled, long_day, heat, meds) record WHY a day might look off; small_child = a small child broke the night, a known cause outside training — never read that night as overreaching. Record them as ticked; never fold a confounder into the numbers themselves. Values are range-checked (e.g. rhr 25-110) so a typo can't poison the baselines.

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / small_child
      Added value: +{
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / soreness_where
      Added value: +{
+  "description": "where the muscles are sore (soreness 3 or lower): legs, upper body or all over",
+  "enum": [
+    "legs",
+    "upper",
+    "all"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations that only say it is non-read-only and non-destructive, the description discloses idempotent MERGE-upsert behavior, partial-update semantics where existing fields survive, a 90-item batch cap, and range-checking to protect baselines. These are exactly the behavioral details an agent needs before writing readiness data.

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?

The description is a single dense paragraph but is front-loaded with the core operation and idempotency contract, then moves through batch behavior, field categories, and confounder semantics. Every clause carries useful information for correct invocation.

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 complex nested write tool with no output schema and no property descriptions, the description is largely complete: it covers idempotency, batching, field semantics, and confounders. It leaves minor gaps around return shape and a few fields like note and other_confounder.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the burden and does so well: it defines McLean 1-5 scales, prs 0-10, optional objective fields with units, confounder flags, and an example range check. It does not document every minor field such as note or other_confounder, but it adds substantial meaning beyond the schema.

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 states a specific verb and resource: record the athlete's daily readiness, one entry per date, via an idempotent MERGE-upsert. This clearly distinguishes it from the sibling read tools such as get_readiness and get_readiness_today.

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 gives clear usage context, including one-entry-per-date semantics and batch backfill from an export. However, it does not explicitly name get_readiness/get_readiness_today as alternatives or state when not to use this tool.

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

All Blocks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources