Skip to main content
Glama

Club OS by Cotlet

Manage pt agreement freeze in Club OS

club_os_manage_pt_agreement_freeze
Read-onlyIdempotent

Manage pt agreement freeze 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_manage_pt_agreement_freeze"
  }
}

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 description adds meaningful behavior beyond the annotations by clarifying that the tool opens nothing itself and only returns step-by-step screens, buttons, and fields. It also discloses the API credential limitation, which is useful context for an agent considering alternate integration paths.

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 definition is generally front-loaded and understandable, but the API credential sentence is long and somewhat tangential, and phrases like 'from ChatGPT, Claude or any AI agent' add little. It could be tightened without losing important meaning.

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?

Given zero parameters, no output schema, and read-only annotations, the description is complete enough: it explains what is returned and how to proceed. It could be slightly stronger by explicitly noting that no actual freeze occurs and by naming likely sibling alternatives.

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 has zero parameters, so there are no parameter semantics to document, and the description appropriately does not invent any. The baseline for a zero-parameter tool applies.

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 resource and outcome: it returns step-by-step instructions for managing a PT agreement freeze in Club OS. It is clear this is an instructional tool rather than a direct mutation, though it does not explicitly distinguish itself from sibling freeze 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?

The description explains the intended workflow: get Club OS instructions here, then use cotlet_browser_* tools to perform the action. However, it gives no explicit guidance on when to use this tool versus siblings such as club_os_freeze_a_member_account or other PT agreement tools.

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