Skip to main content
Glama
My Gym Stats MCP

My Gym Stats MCP

Read one logbook month

read_logbook_month
Read-onlyIdempotent

Reads every worksheet from the monthly workout logbook selected by year and month, letting you review training data without handling file IDs, paths, URLs, or ranges.

Instructions

Read every worksheet from the single monthly logbook spreadsheet selected by year and month. File IDs, paths, URLs, and ranges 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>",
      "month": "<month>"
    },
    "name": "read_logbook_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit logbook year
monthYesCalendar month number from 1 to 12

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 behavior, so the safety profile is covered. The description adds genuinely new context: file IDs, paths, URLs and ranges are resolved and restricted server-side, telling the agent it need not and cannot supply them. Return shape is covered by the output schema, so no further gap is material.

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 tight sentences with zero filler. The read scope is front-loaded and the server-resolution caveat follows in a single supporting clause.

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 rich annotations, a full output schema and fully documented parameters, the description only needs to state scope and any server-side constraints, which it does. The one remaining gap is routing guidance against the year and entire-logbook siblings.

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 coverage is 100% with both parameters documented (four-digit year, month 1-12). The description confirms that year and month select the spreadsheet but adds no format or boundary detail beyond the schema, so the schema carries the weight.

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?

A specific verb ('Read') plus resource ('every worksheet from the single monthly logbook spreadsheet') and a precise selector ('year and month'). The word 'single monthly' implicitly delimits it from read_entire_logbook and read_logbook_year, though no sibling is named 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 implied by the scope ('single monthly spreadsheet'), so an agent can infer this is the one-month-at-a-time option. However, there is no explicit when-to-use versus read_entire_logbook or read_logbook_year, and no stated exclusions or cost trade-offs between them.

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