Skip to main content
Glama

MFIT Personal

by io.github.mcp-dir

mfit_workout_delete_exercise

Destructive

Destructive operations on workout routines, sessions, and exercises. Actions: delete_routine — soft-delete a routine (moves to "Excluídas"; reversible) delete_session — remove a session from a routine (irreversible) delete_exercise — remove an exercise from a session (irreversible). Get exercise_session_id from mfit_workout get_session → exerciciosMontados.k{id}[0].idExercSession.

[Flattened action: delete_exercise]

Bulk support: accepts routine_ids, session_ids, exercise_session_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
routine_idNo
session_idNo
routine_idsNo
session_idsNo
exercise_session_idNo
exercise_session_idsNo

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description adds value by clarifying that delete_exercise is irreversible and specifying how to get exercise_session_id from another tool. Also mentions bulk support, enhancing transparency.

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

Conciseness3/5

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

The description is fairly long and includes a bullet list and flattened action note. It is structured but contains extraneous information (other actions) that could be omitted for the specific tool.

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

Completeness2/5

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

Given 7 parameters with 0% coverage and no output schema, the description should be thorough. It covers only a few parameters and does not explain return values or error behavior, leaving significant gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It mentions routine_ids, session_ids, exercise_session_ids for bulk and exercise_session_id in the hint, but fails to describe account, routine_id, session_id, leaving many parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description includes multiple destructive actions (delete_routine, delete_session, delete_exercise) beyond the tool's name, which focuses on delete_exercise. While it specifies the delete_exercise action and provides a hint, the mixed purpose reduces clarity, especially with sibling tools for routine and session deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions bulk support and provides a hint on obtaining exercise_session_id, but does not explicitly guide when to use this tool over siblings like mfit_workout_delete_routine or mfit_workout_delete_session. The 'Flattened action: delete_exercise' note is helpful but not sufficient.

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

All MFIT Personal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0
Disambiguation1/5

Many tools have identical descriptions but different names (e.g., mfit_client_get, mfit_client_list, mfit_client_list_groups all share the same description text). The flattened action pattern creates multiple tools for each action, making it extremely difficult for an agent to choose the correct one. Tools like mfit_workout_write_add_exercise and mfit_workout_write_archive_routine share the same verbose description, leading to high ambiguity.

Naming Consistency2/5

The naming follows a loose mfit_<domain>_<action> pattern, but there is inconsistency: some tools use 'get' (mfit_get_client_count), others use 'list' (mfit_client_list), and actions like 'write' are overloaded with multiple sub-actions. The pattern is not uniform, and the flattened action suffix adds confusion.

Tool Count2/5

With 48 tools, the count is excessive for what appears to be a single-domain server (personal training management). Many tools are redundant because they only differ by a single action parameter. The number could be reduced significantly by consolidating related operations.

Completeness3/5

The server covers a wide range of functionality: client management, workouts, exercises, files, finances, retention, and feedback. However, there are notable gaps such as direct messaging, advanced analytics, or payment processing. The duplication of tools also suggests that the actual feature set is less complete than the tool count implies.

Resources