Skip to main content
Glama

MoveMate: Gym Workout Tracker

Search exercises

search_exercises
Read-only

Looks up exercises in MoveMate's library (including the user's own custom exercises) and returns their exercise_id and exercise_type. Renders nothing for the user — it is the lookup for building or editing a workout. The model must only compose workouts from exercises returned here — never invented ones. Resolve every exercise a workout needs in ONE call: pass all their names in queries rather than calling once per exercise. Each result carries an exercise_type saying how that movement is measured (reps, time, distance, or speed and level on a cardio machine) — it decides which target fields create_planned_workout will accept for it, so read it before writing sets. To show exercises to the user ("what can I do for chest?"), call show_exercises instead.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many exercises to return. Default 20, max 50. With queries it is per name: default 5, max 20.
queryNoOne exercise name or part of it, fuzzy-matched — e.g. "bench press" or "romanian". Omit to browse by muscle_group or equipment.
queriesNoSeveral exercise names to resolve at once — e.g. every exercise of the workout being built. Each is fuzzy-matched on its own; results come back flat, each tagged with the matched_query it answers. Up to 30.
equipmentNoEquipment name, e.g. "dumbbell", "barbell", "kettlebell" or "bodyweight". Common synonyms are accepted.
muscle_groupNoMuscle group name. Broad lower-body aliases are supported: legs, leg, lower body, and lower-body include quads, hamstrings, glutes, calves, abductors, and adductors. Also accepted: full body, cardio, inner/outer thigh.

Output Schema

NameRequiredDescriptionDefault
localeYes
exercisesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / queries / description
      Previous value: -"Several exercise names to resolve at once — e.g. every exercise of the workout being built. Each is fuzzy-matched on its own; results come back flat, each tagged with the matched_query it answers. Up to 15."New value: +"Several exercise names to resolve at once — e.g. every exercise of the workout being built. Each is fuzzy-matched on its own; results come back flat, each tagged with the matched_query it answers. Up to 30."
    • changedInput schema / properties / queries / maxItems
      Previous value: -15New value: +30
  2. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many exercises to return. Default 20, max 50."New value: +"How many exercises to return. Default 20, max 50. With queries it is per name: default 5, max 20."
    • addedInput schema / properties / queries
      Added value: +{
      +  "description": "Several exercise names to resolve at once — e.g. every exercise of the workout being built. Each is fuzzy-matched on its own; results come back flat, each tagged with the matched_query it answers. Up to 15.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 15,
      +  "type": "array"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Exercise name or part of it, fuzzy-matched — e.g. \"bench press\" or \"romanian\". Omit to browse by muscle_group or equipment."New value: +"One exercise name or part of it, fuzzy-matched — e.g. \"bench press\" or \"romanian\". Omit to browse by muscle_group or equipment."
    • addedOutput schema / properties / exercises / items / properties / matched_query
      Added value: +{
      +  "description": "With queries: the name this result was found for.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedOutput schema / properties / exercises / items / properties / exercise_type / description
      Previous value: -"How this movement is measured, and therefore which targets a set for it accepts: default = weight and reps (most strength work, and bodyweight work with reps such as pull-ups or hill sprints); time = duration only (planks, dead hangs, skipping); time_weight = duration and weight (weighted plank, farmer hold); distance_time = distance and duration (running, rowing machine, treadmill, cycling); weight_distance = weight and distance (farmer walk, sled push)."New value: +"How this movement is measured, and therefore which targets a set for it accepts: default = weight and reps (most strength work, and bodyweight work with reps such as pull-ups or hill sprints); time = duration only (planks, dead hangs, skipping); time_weight = duration and weight (weighted plank, farmer hold); distance_time = distance and duration (outdoor running, cycling or swimming, rowing machine, SkiErg — anything whose monitor shows distance rather than km/h); weight_distance = weight and distance (farmer walk, sled push); cardio_machine = speed in km/h, the machine level (incline or resistance) and duration — treadmill, stationary bike, stepmill; distance is derived from speed and time. Continuous cardio (cardio_machine, distance_time) is ONE set per session — a 20-minute treadmill walk is a single set of 1200 seconds, not three."
    • changedOutput schema / properties / exercises / items / properties / exercise_type / enum
      Previous value: -[
      -  "default",
      -  "time",
      -  "time_weight",
      -  "distance_time",
      -  "weight_distance"
      -]New value: +[
      +  "default",
      +  "time",
      +  "time_weight",
      +  "distance_time",
      +  "weight_distance",
      +  "cardio_machine"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / muscle_group / description
      Previous value: -"Muscle group name. Broad lower-body aliases are supported: legs, leg, lower body, and lower-body include quads, hamstrings, glutes, and calves."New value: +"Muscle group name. Broad lower-body aliases are supported: legs, leg, lower body, and lower-body include quads, hamstrings, glutes, calves, abductors, and adductors. Also accepted: full body, cardio, inner/outer thigh."
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly and non-destructive annotations, the description discloses that the tool renders nothing for the user and returns exercise_id plus exercise_type. It also explains that exercise_type determines which target fields create_planned_workout will accept, which is important behavioral context for downstream use.

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?

The description is dense but well structured: purpose first, then output behavior, then the no-invented-exercises constraint, then batching guidance, then downstream exercise_type implications, then the show_exercises alternative. Every sentence has a clear operational purpose.

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

Completeness5/5

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

Given the annotations, 100% schema coverage, and an output schema, the description provides everything an agent needs to choose the tool, batch queries correctly, avoid invented exercises, and interpret exercise_type before calling create_planned_workout. It also routes the user-facing display case to the correct sibling tool.

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?

Schema coverage is 100%, so the schema already documents query, queries, limit, equipment, and muscle_group in detail. The description still adds meaningful operational semantics, especially that queries should carry all exercise names for one batched resolution, and that exercise_type affects how results can be used downstream.

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?

The description states a specific verb and resource: it looks up exercises in MoveMate's library, including custom exercises, and returns exercise_id and exercise_type. It also distinguishes this lookup from show_exercises, which is for displaying exercises to the user.

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?

It explicitly says to use this tool when building or editing a workout and to call show_exercises instead when showing exercises to the user. It also gives a clear batching instruction: resolve every needed exercise in one call by passing all names in queries rather than calling once per exercise.

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