Skip to main content
Glama

Club OS by Cotlet

Configure workout nutrition templates in Club OS

club_os_configure_workout_nutrition_templates
Read-onlyIdempotent

Configure workout nutrition templates 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_configure_workout_nutrition_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description reinforces and extends this by stating it 'opens nothing by itself' and requires a separate browser step, which is the critical behavioral fact for an agent to plan a two-phase workflow. The API-availability note adds external context. It does not describe the length or format of the returned steps in detail, keeping it short of a 5.

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 handoff to cotlet_browser_* tools are front-loaded and earn their place. The trailing sentence about Club OS's official API is somewhat tangential to the tool's operation, though it does prevent a dead-end investigation by the agent.

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?

For a zero-parameter, no-output-schema guidance tool, the description covers the essentials: what it returns (step-by-step screens, buttons, fields), that it performs no write itself, and which tools complete the action. Nothing an agent needs in order to call it correctly 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 there is nothing to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed beyond the account context, without introducing confusion.

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

Purpose5/5

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

States a specific verb and resource ('Configure workout nutrition templates') scoped to 'the user's own Club OS account', and immediately clarifies the tool's real output: a step-by-step guide rather than an action. It explicitly differentiates itself from the acting tools ('opens nothing by itself; then do it with the cotlet_browser_* tools'), so an agent can tell what it produces versus what the browser siblings do.

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?

Gives a clear usage pattern: call this first to get screens/buttons/fields, then execute the steps with the cotlet_browser_* tools in the Cloud Browser. It also notes the official API alternative and its blocker (credentials only via email to Club OS support), which helps an agent rule out an API path. It does not explicitly distinguish this from the many other club_os_configure_* siblings, leaving some selection inference to the agent.

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