Skip to main content
Glama

View Gymdesk invoices in Gymdesk

gymdesk_view_gymdesk_invoices
Read-onlyIdempotent

View Gymdesk invoices 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_gymdesk_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: it explicitly says it opens nothing, that it returns procedural content rather than data, and that execution depends on the Gymdesk Cloud Browser being available. The note about no public Gymdesk API also explains why the browser route is required, which an agent cannot infer from annotations alone.

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?

The core behavior and the required follow-up tool family are front-loaded in the first two sentences, which is where they belong. The trailing API-availability sentence is a bit long and reads like provenance justification, but it does explain the browser requirement, so it earns most of its space.

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?

With no output schema, the description carries the burden of describing the return value, and it does: step-by-step screens, buttons, and fields. It also covers the execution path (cotlet_browser_* in the user's Cloud Browser) and the reason an official API route is unavailable, so an agent has everything needed to call it and act on the result.

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 baseline is 4; there is no parameter meaning to add. The description correctly introduces no parameter talk, keeping expectations aligned with the empty schema.

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?

The description states a specific verb and resource ('View Gymdesk invoices') and then immediately clarifies the real behavior: it returns step-by-step Gymdesk instructions (screens, buttons, fields) rather than invoice data. That clarification is essential and prevents a misread of the name, though it never contrasts itself with the sibling invoice/payment-history tool.

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 handoff rule: this tool 'opens nothing by itself', so the actual action must be performed with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. That is useful sequencing guidance, but there is no guidance on when to prefer the sibling 'view_member_payment_history_recurring_payments_and_invoi' or other export tools, so selection among invoices-related tools 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources