Skip to main content
Glama

find_exercises

Find exercises that target specific muscles with filters for equipment, difficulty, movement pattern, and exercise type to customize workout plans.

Instructions

Find exercises that target a specific muscle, with optional filters. Use search_muscles first if you don't know the muscle ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
muscleYesMuscle ID or name (e.g. 'pectoralis_major_sternal')
equipmentNoFilter by equipment type
difficultyNoFilter by difficulty level
movement_patternNoFilter by movement pattern
exercise_typeNoFilter by exercise type
roleNoFilter by muscle role
limitNoMax results (default: 50)

Implementation Reference

  • The handler for the 'find_exercises' tool, which takes a muscle and optional filters, calls the client.findExercises method, and returns the result as JSON.
    server.tool(
      "find_exercises",
      "Find exercises that target a specific muscle, with optional filters. " +
        "Use search_muscles first if you don't know the muscle ID.",
      {
        muscle: z.string().describe("Muscle ID or name (e.g. 'pectoralis_major_sternal')"),
        equipment: z
          .enum([
            "barbell", "dumbbell", "kettlebell", "cable", "machine", "bodyweight",
            "band", "smith_machine", "trap_bar", "ez_bar", "suspension",
            "medicine_ball", "plate", "landmine", "none",
          ])
          .optional()
          .describe("Filter by equipment type"),
        difficulty: z
          .enum(["beginner", "intermediate", "advanced"])
          .optional()
          .describe("Filter by difficulty level"),
        movement_pattern: z
          .enum([
            "horizontal_push", "horizontal_pull", "vertical_push", "vertical_pull",
            "squat", "hinge", "lunge", "carry", "rotation", "anti_rotation",
            "flexion", "extension", "isolation", "abduction", "adduction",
          ])
          .optional()
          .describe("Filter by movement pattern"),
        exercise_type: z
          .enum(["compound", "isolation", "isometric"])
          .optional()
          .describe("Filter by exercise type"),
        role: z
          .enum(["primary", "secondary", "stabilizer"])
          .optional()
          .describe("Filter by muscle role"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(200)
          .optional()
          .describe("Max results (default: 50)"),
      },
      async ({ muscle, ...filters }) => {
        try {
          const result = await client.findExercises(muscle, filters);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (err) {
          return { content: [{ type: "text", text: formatError(err) }], isError: true };
        }
      },
    );
  • src/tools.ts:49-99 (registration)
    Registration of the 'find_exercises' tool using server.tool in src/tools.ts.
    server.tool(
      "find_exercises",
      "Find exercises that target a specific muscle, with optional filters. " +
        "Use search_muscles first if you don't know the muscle ID.",
      {
        muscle: z.string().describe("Muscle ID or name (e.g. 'pectoralis_major_sternal')"),
        equipment: z
          .enum([
            "barbell", "dumbbell", "kettlebell", "cable", "machine", "bodyweight",
            "band", "smith_machine", "trap_bar", "ez_bar", "suspension",
            "medicine_ball", "plate", "landmine", "none",
          ])
          .optional()
          .describe("Filter by equipment type"),
        difficulty: z
          .enum(["beginner", "intermediate", "advanced"])
          .optional()
          .describe("Filter by difficulty level"),
        movement_pattern: z
          .enum([
            "horizontal_push", "horizontal_pull", "vertical_push", "vertical_pull",
            "squat", "hinge", "lunge", "carry", "rotation", "anti_rotation",
            "flexion", "extension", "isolation", "abduction", "adduction",
          ])
          .optional()
          .describe("Filter by movement pattern"),
        exercise_type: z
          .enum(["compound", "isolation", "isometric"])
          .optional()
          .describe("Filter by exercise type"),
        role: z
          .enum(["primary", "secondary", "stabilizer"])
          .optional()
          .describe("Filter by muscle role"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(200)
          .optional()
          .describe("Max results (default: 50)"),
      },
      async ({ muscle, ...filters }) => {
        try {
          const result = await client.findExercises(muscle, filters);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (err) {
          return { content: [{ type: "text", text: formatError(err) }], isError: true };
        }
      },
    );
Behavior2/5

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

No annotations provided, so description carries full burden. Only states basic operation ('Find exercises') without disclosing return format, pagination behavior beyond the limit parameter, read-only nature, or error handling. Does not mention what data structure is returned.

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 establishes purpose and capability; second provides prerequisite workflow. Well-structured and appropriately sized for the tool's complexity.

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 7-parameter lookup tool with no output schema or annotations. Covers primary use case and prerequisite workflow. Lacks output format disclosure and error scenario documentation, which is notable given the rich enum parameter set (5 enums) and absence of structured behavioral metadata.

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 has 100% description coverage, establishing baseline 3. Description mentions 'optional filters' generally but adds no semantic depth beyond the schema's existing enum descriptions and type definitions. Second sentence clarifies muscle accepts ID or name, which aligns with parameter description but adds workflow context.

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?

Clear verb ('Find') and resource ('exercises') with specific scope ('target a specific muscle'). Mentions prerequisite workflow with search_muscles, implicitly distinguishing from that sibling. However, does not explicitly differentiate from 'search_exercises' sibling, leaving potential ambiguity about when to use which search tool.

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?

Explicitly states prerequisite: 'Use search_muscles first if you don't know the muscle ID.' This provides clear workflow guidance. Missing explicit 'when not to use' guidance regarding 'search_exercises' alternative.

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