Gymdesk by Cotlet

View account plan in Gymdesk

gymdesk_view_account_plan

Read-onlyIdempotent

View account plan in the user's own Gymdesk account from ChatGPT, Claude or any AI agent. Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. Gymdesk's official API: No publicly documented Gymdesk API was found on 11 Nov 2026: gymdesk.com/api, gymdesk.com/developers and docs.gymdesk.com/api returned 404 and the help center has no Gymdesk API article.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description explicitly says it 'opens nothing by itself,' so the agent knows the call has no side effects and is only a preparation step. It also discloses there is no official Gymdesk API, explaining why browser automation is required. It does not describe the granularity of the returned steps.

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 core behavior and the required follow-up are front-loaded and efficient. The third sentence, citing three specific URLs that returned 404 on a specific date, is more forensic detail than an agent needs to select and call the tool.

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

Completeness4/5

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

With no parameters and no output schema, the description does the necessary work: it says what is returned (screens, buttons, fields), that nothing is executed, and what tool family to use next. Only the exact form of the returned guidance is left unspecified, which is minor.

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?

The tool takes zero parameters, so the schema carries no semantics to compensate for and the baseline of 4 applies. The description correctly implies no input is needed.

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

Purpose4/5

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

Names a specific verb and resource (view the account plan) and immediately clarifies the actual mechanism: it returns step-by-step Gymdesk instructions rather than plan data. This resolves the ambiguity in the name/title, though it never distinguishes itself from the many sibling gymdesk_view_* tools.

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?

It gives a clear follow-on path — execute the returned steps using the cotlet_browser_* tools in the Gymdesk Cloud Browser — which implies usage context. However, it states no when-not conditions and does not indicate when an agent should prefer a sibling reporting tool over this guidance tool.

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

All Gymdesk by Cotlet 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?