Skip to main content
Glama

get_routine_folder

Retrieve a routine folder by its unique folder ID. Access organized workout routines for efficient training management.

Instructions

Fetch a single routine folder by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for `get_routine_folder`. Fetches a single routine folder by its ID via GET /routine_folders/{folder_id}.
    @mcp.tool()
    @tool_guard
    async def get_routine_folder(folder_id: int) -> dict[str, Any]:
        """Fetch a single routine folder by id."""
        return {"data": await client.get(f"/routine_folders/{folder_id}")}
  • Registration entry point. `register_all` calls `folders.register(mcp, ctx)`, which registers `get_routine_folder` as an MCP tool (inside folders.py).
    def register_all(mcp, ctx) -> None:
        workouts.register(mcp, ctx)
        routines.register(mcp, ctx)
        folders.register(mcp, ctx)
        templates.register(mcp, ctx)
        webhooks.register(mcp, ctx)
        analytics.register(mcp, ctx)
  • The `register` function in folders.py that uses @mcp.tool() decorator to register `get_routine_folder` as an MCP tool.
    def register(mcp, ctx) -> None:
        client = ctx.client
    
        @mcp.tool()
        @tool_guard
        async def list_routine_folders(page: int = 1, page_size: int = 10) -> dict[str, Any]:
            """List the user's routine folders (e.g. 'Push/Pull/Legs', 'Hypertrophy Block')."""
            return {"data": await client.get("/routine_folders",
                                              params={"page": page, "pageSize": page_size})}
    
        @mcp.tool()
        @tool_guard
        async def get_routine_folder(folder_id: int) -> dict[str, Any]:
            """Fetch a single routine folder by id."""
            return {"data": await client.get(f"/routine_folders/{folder_id}")}
Behavior2/5

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

No annotations provided. Description only states basic action; lacks detail on authentication, error responses, or side effects. Output schema exists but description adds no behavioral context.

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?

Single sentence, front-loaded, no waste. Efficiently conveys core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple fetch operation, but lacks details on error handling and prerequisites. Output schema likely covers return values, so not fully incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. Description mentions 'by id' but does not elaborate on folder_id meaning, format, or constraints beyond the schema's title.

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?

Description clearly specifies verb ('Fetch'), resource ('routine folder'), and key identifier ('by id'). Distinguishes from siblings like 'list_routine_folders'.

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?

Implies use when needing a single folder by ID, contrasting with listing. No explicit when-not or alternatives, but sibling names provide context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vellarasan/hevy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server