MoveMate: Gym Workout Tracker

Show exercises

show_exercises

Read-only

Shows exercises from MoveMate's library (including the user's own custom exercises) to the user as a card grid with images, target muscles and their own history. Use it only when the user wants to see or browse exercises — "what are good chest exercises?", "show me dumbbell moves" — once per request. Not for looking up exercise IDs while building a workout: search_exercises does that without filling the chat. The cards already show names and muscles, so reply with a short comment or recommendation rather than listing them again. Results carry exercise_id and exercise_type like search_exercises, so a follow-up workout can use them directly.

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

Input Schema

Name	Required	Description
`limit`	No	How many exercises to show. Default 20, max 50.
`query`	No	Exercise name or part of it, fuzzy-matched — e.g. "bench press" or "romanian". Omit to browse by muscle_group or equipment.
`equipment`	No	Equipment name, e.g. "dumbbell", "barbell", "kettlebell" or "bodyweight". Common synonyms are accepted.
`muscle_group`	No	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.

Output Schema

Name	Required	Description	Default
`locale`	Yes
`exercises`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare this as a safe read (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavioral context: the output is rendered as visual cards, the agent should respond with a short comment rather than re-listing, and the results carry exercise_id/exercise_type for chaining into a workout. The contrast with search_exercises 'filling the chat' is a useful side-effect disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then routing, then reply-style guidance, then chaining — each sentence contributes something distinct. It is on the long side for a four-parameter read tool, but no sentence is filler.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to add rendering behavior and usage routing — both of which it does. An agent has everything needed to call it correctly and to respond appropriately afterward.

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% and each of the four filters is documented in the schema, including aliases and defaults, so the schema carries the burden. The description adds no filter-specific meaning beyond implying browse-by-muscle/equipment. Baseline 3 is appropriate.

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 a specific verb and resource ('Shows exercises from MoveMate's library') plus the rendering form (card grid with images, target muscles, history). It explicitly distinguishes itself from search_exercises, so an agent can pick between the two without opening a schema.

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?

Gives explicit when-to-use with concrete user phrasings ('what are good chest exercises?'), an exclusion ('not for looking up exercise IDs while building a workout'), the named alternative (search_exercises), and a frequency constraint ('once per request'). Nothing is left to inference.

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

All MoveMate: Gym Workout Tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?