Skip to main content
Glama

get_folders

Read-onlyIdempotent

List the user's workout folders with folder_id, name and workout count. Ids are for tool calls only; never show them to the user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
foldersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / folders / items / properties / folder_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / folders / items / required
      Previous value: -[
      -  "name",
      -  "workout_count"
      -]New value: +[
      +  "folder_id",
      +  "name",
      +  "workout_count"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine behavioral constraint the annotations cannot express: folder ids exist only for tool calls and must never be surfaced to the user, which directly shapes how an agent presents results. It does not discuss pagination or ordering, but for a small folder list that is minor.

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: the first front-loads what is returned, the second carries the one non-obvious operational rule. Every sentence earns its place with no 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?

An output schema exists, so the description does not need to explain return values, and with zero parameters the surface area is small. What it does provide, the field list and the id-handling rule, covers what an agent needs to call and present results correctly; only explicit sibling routing is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema. Baseline for a no-parameter tool applies, and the description correctly spends no words on inputs.

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 names a specific verb and resource ("List the user's workout folders") and even enumerates the returned fields (folder_id, name, workout count), so an agent can tell this is a top-level enumeration tool rather than a detail fetch. It does not explicitly contrast itself with sibling list tools like get_programs or get_workout_templates, which keeps it a step below 5.

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: the word "List" signals a discovery/enumeration call, and the note about ids hints this is a precursor step for tools that take a folder_id. There is no explicit statement of when to call this versus get_workout_detail or get_workout_templates, and no prerequisite or exclusion is given.

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.

Resources