List all MFIT accounts linked to this install.
Returns each account's id, email, label, and an "is_default" flag (true when only one is linked — no need to pass account in other tools). When multiple accounts are linked, every other mfit_* tool accepts an optional account parameter; pass id, email, or label (full or partial).
| Name | Required | Description | Default |
|---|---|---|---|
| account | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds valuable context about return fields, is_default semantics, and how other tools consume account info. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single paragraph packs essential info without redundancy. Front-loaded with main action. Could benefit from slight structuring, but no wasted sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and one optional param, description sufficiently covers purpose, return fields, and integration with sibling tools. Lacks explicit return structure but is functional for agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has one optional param 'account' with 0% description coverage. Description mentions account in context of other tools but does not clarify whether this tool accepts it or its purpose here. Ambiguous, leaving a gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'List all MFIT accounts linked to this install' with specific verb and resource. Lists return fields (id, email, label, is_default) and distinguishes from siblings by being the account listing tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly explains when to use this tool (first step) and how output is used by other tools (account parameter). Tells when account param is optional based on is_default flag, providing clear usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.