Skip to main content
Glama

Club OS by Cotlet

Waive mms invoice payment in Club OS

club_os_waive_mms_invoice_payment
Read-onlyIdempotent

Waive mms invoice payment in the user's own Club OS account from ChatGPT, Claude or any AI agent. Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser. Club OS's official API: Club OS has an official API for its calendar, agreements, leads, follow-ups and KPIs, but credentials come only by emailing Club OS support to set up an account (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": "club_os_waive_mms_invoice_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive, and the description is consistent with them: it explicitly says the tool 'opens nothing by itself' and returns screens/buttons/fields guidance, which reconciles a seemingly mutating name with readOnlyHint=true. It also notes the official-API alternative and its email-support credential gate, adding context beyond the annotations.

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 next step are front-loaded in the first sentence, which is good. But the trailing sentence about Club OS's official API covering calendar, agreements, leads, follow-ups and KPIs is tangential boilerplate that does not mention invoice payments and 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?

For a zero-parameter, no-output-schema guidance tool, the description covers what is returned (step-by-step screens, buttons, fields) and what to do next, which is the information an agent needs. The only shortfall is the unrelated API footnote, which adds noise rather than completing the picture for waiving an invoice.

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 there is no parameter semantics to document and the baseline is 4. The description correctly implies no inputs are needed by framing the result as generic step-by-step instructions.

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+resource (waive an MMS invoice payment in Club OS) and clarifies that the tool itself only returns step-by-step instructions rather than performing the action. It is clear what the agent gets back, though 'mms' is unexplained jargon and the guidance-vs-action framing takes a full clause to parse.

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 does explain the downstream workflow — call cotlet_browser_* tools in the Club OS Cloud Browser to actually waive the invoice — which is useful routing. However, it never distinguishes this from related siblings such as club_os_write_off_an_invoice or club_os_comp_an_invoice, nor says when a waiver is or isn't the right remedy.

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