Skip to main content
Glama
My Gym Stats MCP

My Gym Stats MCP

List logbook files

list_logbook_files
Read-onlyIdempotent

Lists the monthly workout logbook spreadsheets stored in year folders under the configured Google Drive 'logbook' folder, so you can identify available training records.

Instructions

List the monthly Google Spreadsheets contained in YYYY year folders directly under the configured Google Drive folder named "logbook". The root folder is fixed by the server and cannot be selected 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": "list_logbook_files"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
filesYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description still adds genuinely new behavioral context: the root 'logbook' folder is server-fixed and not caller-selectable, which stops an agent from hunting for a path parameter that does not exist.

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 core scope ('monthly spreadsheets in YYYY folders under logbook') is front-loaded before the constraint clause. Every sentence carries information an agent needs.

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 zero parameters, an output schema, and full annotation coverage, this is a simple read tool and the description covers scope plus the key constraint. It omits edge behavior such as what happens when the logbook folder is absent or empty, which would round it out.

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?

The tool takes zero parameters, so the baseline is 4, but the sentence about the fixed root folder is essentially a restatement of the empty schema rather than added nuance. It usefully warns the caller that no folder argument exists, yet contributes little beyond that.

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 uses a specific verb ('List') plus a precise resource ('monthly Google Spreadsheets contained in YYYY year folders') and even states the two-level folder layout, so an agent knows exactly what comes back. It does not name any sibling tool, but 'list' versus the 'read_*' siblings is distinguishable from the verb alone.

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: an agent can infer this is the discovery step before reading a specific month or year, but the description never says when to call it instead of read_logbook_month or read_entire_logbook. There are no explicit exclusions or preconditions.

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