Skip to main content
Glama

Get a day's session

get_today
Read-onlyIdempotent

Returns a day as the phone's Today screen will show it: the coach session if one is stored, otherwise the program day at the current ladder levels, or a rest day. Nothing is adjusted. date defaults to today in the athlete's time zone. A day that has started or finished is returned as stored. parts lists the day's sessions (one on an unsplit day; a split day has 2–3, each with its label, and a started or finished part is returned as stored while the others are still planned). plan is the part in progress, else the first unfinished one, else the last; status is in_progress if any part is, completed once every part has ended, otherwise planned. It shows what the athlete has planned, before or after a write.

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

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the three-way resolution fallback, that 'nothing is adjusted' (no recalculation or materialization on read), that started or finished days come back exactly as stored, and that unstarted parts remain 'planned'. It also defines the status derivation (in_progress if any part, completed once every part has ended, otherwise planned), which is real behavioral detail not derivable from structured fields.

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?

Front-loaded with the resolution order, then the default/date semantics, then the return-shape explanation. No filler sentences, but the parts/plan/status material is packed into one dense stretch and could be broken up for easier scanning.

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?

No output schema exists, so the description carries the return contract and does so: `parts` cardinality and labeling on split days, the `plan` selection rule (in-progress, else first unfinished, else last), and the `status` values. Combined with annotation coverage of the safety profile, an agent has enough to call and interpret this correctly; only date edge-case behavior is left implicit.

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?

With 0% schema description coverage, the description must compensate for the single `date` parameter, and it does supply the key semantics: the default is today in the athlete's time zone. The ISO format itself is carried by the schema pattern. It stops short of saying what a past or future date returns, which is the only meaningful gap.

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?

States a specific verb and resource ('Returns a day') and immediately qualifies what gets returned: the coach session if stored, else the program day at current ladder levels, else a rest day. The framing 'as the phone's Today screen will show it' plus 'Nothing is adjusted' distinguishes it unambiguously from the write-side siblings such as set_today_session.

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?

Usage is implied rather than stated: 'Nothing is adjusted' and 'before or after a write' signal this is the read-side view to consult around mutations, and the observation that a started or finished day is returned as stored hints at refresh semantics. However, no sibling is named and there is no explicit when-not guidance (e.g. use get_logs for historical data instead).

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