Skip to main content
Glama

Training overview

get_training_overview
Read-only

A snapshot of the user right now: their active split, this week's workouts (done, missed and still planned), totals vs last week, today's plan, recent body weight, and their nutrition goal (lose fat / maintain / build muscle) with daily calorie and macro targets and what they've eaten today. Use this first — for training AND for any question about what or how much to eat. get_nutrition has the full food log.

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_training_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds the material thing annotations cannot: exactly what data comes back, including that missed workouts and week-over-week deltas are present. Since no output schema exists, this return-content disclosure is doing real work, though it does not mention freshness/staleness or empty-state behavior.

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?

Two sentences, no filler, and the long enumeration is justified because it is the only specification of the return payload. Minor deduction: the most decision-relevant instruction ('Use this first') sits after the field list rather than being front-loaded.

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 no-argument read tool with no output schema, this is complete: it fully describes the returned payload, states the tool's primacy in the workflow, and hands off to get_nutrition for the one adjacent need it does not serve. Nothing an agent needs in order to call 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?

Zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies no inputs are needed by framing the result as an implicit 'right now' snapshot rather than requiring a date or user argument.

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?

Names a specific artifact (a current snapshot of the user) and enumerates its contents precisely: active split, this week's workouts done/missed/planned, week-over-week totals, today's plan, recent body weight, and nutrition goal with calorie/macro targets and intake so far. It then explicitly distinguishes itself from get_nutrition, so an agent can pick it over that sibling 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit ordering directive ('Use this first') plus the two question classes it covers (training and anything about what or how much to eat), and routes the excluded case — the full food log — to get_nutrition. That is when-to-use, scope, and alternative in two sentences.

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