MoveMate: Gym Workout Tracker

Create custom exercise

create_custom_exercise

Adds a new exercise to the user's own library, for when search_exercises doesn't have what they're after — including conditioning work such as a run, skipping or sprints, via exercise_type. The returned exercise_id can then be used with search_exercises results in create_planned_workout — never invent an exercise_id. Not safe to retry: calling this again with the same name creates a separate duplicate exercise, not the same one — check search_exercises first if unsure whether it already exists.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Exercise name as the user will see it in the app, e.g. "Incline hammer curl". Max 80 characters.
`notes`	No	Optional setup or coaching cues shown with the exercise. Max 500 characters.
`equipment`	No	Free text, e.g. "dumbbell" — best-effort matched against the library; omitted if no match.
`muscle_group`	No	Free text, e.g. "chest" or "hamstrings" — best-effort matched against the library; omitted if no match.
`exercise_type`	No	How the movement is measured. This decides which targets create_planned_workout will accept for it and which inputs the app shows while training, and there is no tool to change it afterwards — pick it deliberately. Defaults to "default". 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).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`exercise_id`	Yes
`exercise_type`	Yes
`equipment_matched`	Yes
`muscle_group_matched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare idempotentHint=false and destructiveHint=false, but the description goes further with the concrete consequence: re-calling with the same name creates a separate duplicate rather than the same exercise, and it warns never to invent an exercise_id. It also discloses that exercise_type cannot be changed afterwards because no tool exists for it.

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?

Three sentences, each earning its place: creation scope, how to use the returned id, and the non-idempotency warning. The most consequential caveats (duplicate creation) are stated directly rather than buried.

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 so return values need no prose, yet the description still ties the returned exercise_id to the next tool in the workflow. For a 5-param mutation with an irreversible enum, all decision-relevant context is present.

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 baseline is 3, but the description adds meaning the schema does not: exercise_type determines which targets create_planned_workout will accept and is immutable post-creation. That cross-tool consequence is genuine added value beyond the schema's own enum documentation.

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 ('Adds a new exercise to the user's own library') and immediately distinguishes it from the sibling search_exercises, including the conditioning-use case via exercise_type. An agent can tell exactly what this creates without opening the 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?

Explicitly names the trigger ('for when search_exercises doesn't have what they're after'), the alternative to check first ('check search_exercises first if unsure whether it already exists'), and the downstream consumer ('create_planned_workout'). No condition 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?