Skip to main content
Glama

list_workout_plans

Read-only

List a client's workout plans (id, title, dates, and the PDF it came from if any). Pass the client's user _id. This does NOT include the exercises — call get_workout_plan with a plan _id to read them.

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": {
      "clientId": "<clientId>"
    },
    "name": "list_workout_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful content shape (four fields including the originating PDF) and what is omitted, but says nothing about pagination, result limits, or behavior when the client has no plans.

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?

Three short sentences, zero padding: purpose and returned fields first, required identifier second, the exclusion and escalation path last. Every clause 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?

No output schema exists, and the description compensates by naming the returned fields. Combined with the single required parameter and read-only annotations, an agent has nearly everything needed; only result volume/pagination behavior is unaddressed.

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?

Schema coverage is 0% — clientId carries no description at all — so the description must compensate, and it does: it states the value is the client's user _id, which disambiguates it from the plan _id used by get_workout_plan. It could still say more about format (object id vs email vs username).

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?

Specific verb (List) plus resource (a client's workout plans), with the returned fields enumerated inline (id, title, dates, source PDF). It is immediately distinguishable from get_workout_plan because it states outright that exercises are excluded.

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

Usage Guidelines4/5

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

Gives an explicit exclusion and the correct alternative: exercises require get_workout_plan with a plan _id. It also clarifies the scope is a specific client rather than the caller's own plans, which implicitly separates it from the list_my_plans/list_organization_plans family, though those siblings are never named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.