Skip to main content
Glama
My Gym Stats MCP

My Gym Stats MCP

Read one logbook year

read_logbook_year
Read-onlyIdempotent

Reads every monthly worksheet from a specified logbook year to retrieve complete training data in one call. Use it to access all workout records for a given year without querying each month separately.

Instructions

Read every worksheet from all monthly spreadsheets in one logbook year. The year folder and spreadsheet IDs are resolved and restricted by the server.

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": {
      "year": "<year>"
    },
    "name": "read_logbook_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit logbook year

Output Schema

NameRequiredDescriptionDefault
cellCountYes
spreadsheetsYes
spreadsheetCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds a genuinely non-obvious operational fact: folder and spreadsheet IDs are resolved and access-restricted server-side, so the caller must not supply IDs. It says nothing about payload size or limits when reading a full year of monthly sheets.

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?

Two short sentences with the scope stated first and the server-side resolution constraint second; nothing is redundant or decorative.

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?

With an output schema present, return values need no explanation, and a single required parameter is fully specified in the schema. The only shortfall is behavior for a missing/invalid year and the potential volume of a full-year read, which the description leaves unstated.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter is fully documented with a type, range 1900-2100, and the note 'Four-digit logbook year'. The description repeats the notion of a year but adds no format or edge-case meaning beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource scope: read every worksheet across all monthly spreadsheets for a single year. The 'one logbook year' scope implicitly separates it from read_logbook_month and read_entire_logbook, though it never names those alternatives explicitly.

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 only implied by the scope wording — an agent can infer this is the right tool when it wants a whole year but not the whole logbook. There is no explicit when-to-use, when-not-to-use, or named alternative to disambiguate against the sibling tools.

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