Skip to main content
Glama

get_alternatives

Find alternative exercises based on muscle overlap scores to replace or supplement workouts while targeting similar muscle groups.

Instructions

Find alternative exercises ranked by muscle overlap score. Use search_exercises first if you don't know the exercise ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exerciseYesExercise ID or name
limitNoMax results (default: 10)

Implementation Reference

  • The implementation of getAlternatives in the MusclesWorkedClient that makes the API request.
    async getAlternatives(exercise: string, limit?: number): Promise<unknown> {
      const params = limit !== undefined ? `?limit=${limit}` : "";
      return this.request(
        `/api/v1/exercises/${encodeURIComponent(exercise)}/alternatives${params}`,
      );
    }
  • src/tools.ts:121-143 (registration)
    Registration of the get_alternatives MCP tool.
    server.tool(
      "get_alternatives",
      "Find alternative exercises ranked by muscle overlap score. " +
        "Use search_exercises first if you don't know the exercise ID.",
      {
        exercise: z.string().describe("Exercise ID or name"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(50)
          .optional()
          .describe("Max results (default: 10)"),
      },
      async ({ exercise, limit }) => {
        try {
          const result = await client.getAlternatives(exercise, limit);
          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?

Discloses the ranking behavior (muscle overlap score) which is crucial context, but lacks safety/operational disclosure required due to missing annotations. No mention of error handling for invalid exercise IDs or whether results are cached.

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, zero waste. First sentence establishes purpose and ranking method; second provides the critical usage prerequisite. Purpose is front-loaded.

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?

Adequate for a 2-parameter retrieval tool without output schema. Describes what is returned (ranked alternatives) and the ranking logic. Minor gap: no description of the alternative object structure or error conditions.

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 coverage is 100% with clear descriptions ('Exercise ID or name', 'Max results'). Description reinforces the exercise parameter usage through the ID reference in usage guidelines, but adds no syntax/format details beyond the schema. Baseline 3 appropriate 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?

Excellent specificity: verb (Find) + resource (alternative exercises) + unique ranking mechanism (muscle overlap score). Clearly distinguishes from generic search siblings by specifying the muscle overlap algorithm.

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?

Explicit prerequisite with sibling named: 'Use search_exercises first if you don't know the exercise ID.' Perfectly clarifies the workflow dependency between this tool and search_exercises.

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