Skip to main content
Glama

Club OS by Cotlet

Configure mobile app branding in Club OS

club_os_configure_mobile_app_branding
Read-onlyIdempotent

Configure mobile app branding 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_mobile_app_branding"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 this by stating it opens nothing by itself and returns only instructions. It adds useful context about the required companion browser tooling and the credential constraint on Club OS's official API, though it does not describe output shape beyond "screens, buttons, fields".

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?

Front-loaded with the action and the key constraint (opens nothing, returns a walkthrough), then the follow-up tooling. The final sentence about emailing Club OS support for API credentials is tangential to branding configuration and could be trimmed.

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 a zero-parameter, no-output-schema guidance tool, the description covers what it returns, that it changes nothing, and what to do next. Minor gap: it does not say how detailed or in what format the step-by-step walkthrough arrives.

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 meaning to convey; the description correctly avoids inventing inputs. Baseline for a parameterless schema is a 4.

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 mobile app branding in the user's own Club OS account") and scopes it to the user's own account, which separates it from generic guidance tools. It also clarifies the deliverable is step-by-step instructions rather than an executed change.

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?

Explicitly says the tool "opens nothing by itself" and directs the agent to perform the action with the cotlet_browser_* tools in the Club OS Cloud Browser, which is exactly the when/how guidance needed. It stops short of stating when not to use it or naming alternative configuration 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