Exercise.com by Cotlet

View signed contracts and waivers in Exercise.com

exercise_com_view_signed_contracts_and_waivers

Read-onlyIdempotent

View signed contracts and waivers in the user's own Exercise.com account from ChatGPT, Claude or any AI agent. Returns how to do it in Exercise.com step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Exercise.com Cloud Browser. Exercise.com's official API: Exercise.com has an official API as a paid add-on: "API access is an additional feature with variable pricing", quoted by your Account Representative for your intended usage (checked 11 Nov 2026).

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

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

Behavior3/5

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

The key disclosure is strong: it "opens nothing by itself" and returns a step-by-step walkthrough rather than data, which the readOnlyHint annotation alone would not convey. However, the trailing paragraph about a paid official API is tangential and does not describe return format, limits, or failure behavior, so the behavioral picture is only partly filled in.

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 first two sentences are well structured and front-load the core behavior. The final paragraph on the official API and its variable pricing is long, quoted verbatim, and only loosely connected to invoking this tool, so it dilutes an otherwise tight definition.

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 zero parameters and no output schema, the description supplies most of what an agent needs: the purpose, the fact that it returns guidance rather than performing the action, and the follow-up tool family to use. It could say more about what the returned instructions look like, but nothing critical is missing.

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 imposes no semantic burden and the baseline is 4. The description does not introduce parameter meaning, but none is needed here.

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 names a specific verb and resource (view signed contracts and waivers) and scopes it to the user's own Exercise.com account. It is clear about the deliverable, but it does not distinguish itself from any sibling tool by name, leaving the agent to infer that no other sibling covers contracts/waivers.

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

Usage Guidelines4/5

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

It clearly states the two-step workflow: this tool returns step-by-step instructions, then the agent performs the action with cotlet_browser_* tools in the Cloud Browser. That is actionable context, but there are no explicit exclusions about when not to call it or what to do if the browser tools are unavailable.

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

All Exercise.com 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?