Skip to main content
Glama

Get training logs

get_logs
Read-onlyIdempotent

Returns raw set logs, session feedback, skipped sets and exercise notes (the athlete's words about one exercise, written mid-workout) between two dates (YYYY-MM-DD, inclusive, at most 31 days, to not before from). It has more detail than the summary in get_athlete_context: individual sets, and older stretches of training. A set the athlete corrected at Finish shows their number as value and the player's as loggedValue.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description adds useful behavioral detail: the inclusive date semantics, the 31-day maximum, the ordering constraint on `to` and `from`, and how corrected sets appear as `value` versus `loggedValue`.

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 front-loaded with what the tool returns and then adds only material constraints and distinctions. The parenthetical definition of exercise notes is helpful, and there is no redundant or wasted wording.

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 tool with no output schema, the definition lists the main returned data categories and explains the notable corrected-set representation. It does not describe the exact response structure, ordering, or pagination, but it is otherwise complete enough for an agent to call the tool correctly.

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 must carry parameter meaning. It does this well by specifying YYYY-MM-DD format, inclusive date boundaries, the maximum 31-day range, and the constraint that `to` must not precede `from`.

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 uses a specific verb and resource: returns raw set logs, session feedback, skipped sets, and exercise notes within a date range. It also distinguishes itself from get_athlete_context by noting it has more detail, including individual sets and older training stretches.

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 comparative guidance by naming get_athlete_context's summary as the less detailed alternative and explaining that this tool provides individual sets and older stretches. It does not explicitly state when not to use it, but the selection context is clear.

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