Skip to main content
Glama
Sign In
fitbot-mcp

fitbot-mcp

by alliso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Listar clases del día

list_classes

Get the schedule for a day's fitness classes: times, coaches, spots taken, and your booking status.

Instructions

Lista las clases de un día concreto con su horario, coach, plazas ocupadas y si ya estás apuntado.

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_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFecha en formato YYYY-MM-DD. Si se omite, se usa el día de hoy.
boxIdNoid del box (boid). Solo necesario si tu cuenta pertenece a varios boxes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It implicitly signals a read-only operation ('Lista') and adds useful context about returned fields, but it does not explicitly state that no changes are made, nor does it address dates, auth, or error behavior.

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 a single concise sentence that front-loads the purpose and lists the key returned data. Every word adds value and there is no redundant or vague filler.

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 simple list tool with a well-described schema and no output schema, the description manages to convey the return context (schedule, coach, occupancy, enrollment status). It lacks explicit sibling differentiation, but that gap is largely covered by the clear purpose statement.

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%: the date parameter is described with format and default behavior, and boxId is described with its conditional need. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 the specific verb 'Lista' with resource 'clases de un día concreto' and enumerates useful output details (horario, coach, plazas ocupadas, inscripción). This clearly distinguishes it from sibling tools like book_class, cancel_class, and class_attendees.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus siblings. It does not mention that class_attendees is for viewing attendees of a specific class or that book_class/cancel_class are for actions. The only conditionality noted is the boxId parameter, not tool selection.

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

Deploy Server

Other Tools