Skip to main content
Glama
My Gym Stats MCP

My Gym Stats MCP

Read the entire logbook

read_entire_logbook
Read-onlyIdempotent

Reads all worksheets from every valid monthly spreadsheet in the configured logbook, covering all YYYY folders, to retrieve complete workout history without needing a path or range.

Instructions

Read every worksheet from every valid monthly spreadsheet under all YYYY folders in the configured logbook. No path, file ID, URL, or range can be supplied by the caller.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
cellCountYes
spreadsheetsYes
spreadsheetCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and open-world, so the safety profile is known. The description contributes the key behavioral fact that the read is unfiltered and non-parameterizable — 'No path, file ID, URL, or range can be supplied' — which warns the agent that a full-corpus sweep is the only option. It does not discuss output size, cost, or failure modes (e.g., when no logbook is configured).

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 sentences, no filler, and the scope statement is front-loaded ahead of the constraint. Every sentence carries distinct information.

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?

An output schema exists, so return shape needn't be explained, and annotations cover the safety traits. The remaining ambiguity is minor: 'valid' monthly spreadsheet and the behavior when no logbook/configuration exists are undefined, but an agent can still decide correctly whether to call it.

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 is the baseline 4, and the description reinforces it by explicitly telling the caller that no path, ID, URL, or range may be passed, matching the empty schema with additionalProperties false. Nothing more is required for an argument-free tool.

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 concrete verb and resource ('Read every worksheet from every valid monthly spreadsheet') and defines the scope ('under all YYYY folders in the configured logbook'), which implicitly contrasts with the month- and year-scoped siblings. It stops short of naming those siblings explicitly, so differentiation is inferable rather than stated.

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?

Scope language ('every worksheet', 'all YYYY folders') implies this is the whole-corpus read and that the narrower siblings exist for targeted reads, but no explicit when-to-use or when-not-to-use rule is given. The agent must infer that read_logbook_month or read_logbook_year is preferable when a subset is needed.

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