Skip to main content
Glama

get_morning_training_readiness

Read-only

Retrieve the morning training readiness score for a given date. Evaluates overnight recovery metrics so you can decide whether to train hard or take a rest day.

Instructions

Get morning training readiness score

    Returns the morning training readiness assessment, which evaluates
    recovery status and readiness to train based on overnight metrics.
    Fields match one get_training_readiness entry (the snapshot taken
    right after waking).

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_morning_training_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful domain context (overnight-metric based, single post-waking snapshot) but says nothing about behavior when no data exists for the date, latency, or return shape beyond the field-matching note.

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?

The purpose statement is front-loaded in the first line, followed by supporting context and a short Args block. There is minor docstring residue and some redundancy between 'readiness score' and 'readiness assessment', but nothing that obscures the call.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description explains what the tool returns conceptually, where the values come from, and how they relate to a sibling tool. Nothing an agent needs in order to invoke it correctly is missing.

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

Parameters4/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 carry the parameter meaning, and it does specify the date format as YYYY-MM-DD. It does not clarify whether future dates or dates without a recorded waking are valid, but the format guidance is the key missing piece and it is supplied.

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 names a specific verb and resource ('Get morning training readiness score') and pins down the scope as the morning-only assessment derived from overnight metrics. It explicitly relates itself to the sibling get_training_readiness by saying the fields match a single entry from it, so an agent can tell the two apart without opening either schema.

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 description implies the use case (the snapshot taken right after waking) and references the broader get_training_readiness tool, which hints at when to prefer this one. However, it never states an explicit rule such as 'use this for the morning reading, use get_training_readiness for the full day', so the routing is left to inference.

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

Deploy Server

Other Tools