Skip to main content
Glama

get_muscles_worked

Identify primary, secondary, and stabilizer muscles targeted by specific exercises to optimize workout planning and muscle coverage analysis.

Instructions

Get the primary, secondary, and stabilizer muscles worked by an exercise. Use search_exercises first if you don't know the exercise ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exerciseYesExercise ID or name (e.g. 'barbell_bench_press')

Implementation Reference

  • The MCP tool definition and handler for 'get_muscles_worked'. It uses the provided MusclesWorkedClient to fetch data and handles potential errors using the formatError helper.
    server.tool(
      "get_muscles_worked",
      "Get the primary, secondary, and stabilizer muscles worked by an exercise. " +
        "Use search_exercises first if you don't know the exercise ID.",
      { exercise: z.string().describe("Exercise ID or name (e.g. 'barbell_bench_press')") },
      async ({ exercise }) => {
        try {
          const result = await client.getMusclesWorked(exercise);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (err) {
          return { content: [{ type: "text", text: formatError(err) }], isError: true };
        }
      },
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses output structure (three muscle categories) but does not explicitly confirm read-only safety, error handling when exercises are not found, or rate limiting. The verb 'Get' implies retrieval, but explicit behavioral guarantees are absent.

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 with zero waste: first sentence front-loads core purpose (muscle retrieval with categorization), second sentence gives prerequisite workflow. Every word earns its place; no redundancy with schema or title.

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?

Appropriately complete for a single-parameter lookup tool with 100% schema coverage. The description compensates for missing output_schema by detailing the return structure (primary/secondary/stabilizer muscles) and provides clear sibling references. Minor gap: lacks error handling description for invalid exercise IDs.

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 description coverage is 100% with clear description ('Exercise ID or name') and example ('barbell_bench_press'). Description references 'exercise' and 'exercise ID' but does not add semantic information beyond the schema's documentation, warranting the baseline score for high-coverage schemas.

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?

States specific verb ('Get') plus granular resource scope ('primary, secondary, and stabilizer muscles worked by an exercise'). Distinguishes clearly from siblings like 'search_exercises' (which finds exercises) by focusing on retrieving detailed muscle categorization for a specific known exercise.

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

Usage Guidelines5/5

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

Provides explicit prerequisite workflow: 'Use search_exercises first if you don't know the exercise ID.' This directly names the sibling alternative and defines the exact condition for using that tool instead, guiding correct invocation sequence.

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/csjoblom/musclesworked-mcp'

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