Skip to main content
Glama

Club OS by Cotlet

Manage locker assignments in Club OS

club_os_manage_locker_assignments
Read-onlyIdempotent

Manage locker assignments 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_locker_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself' so the agent knows no Club OS state changes here. It also adds real context beyond annotations: the output shape (screens, buttons, fields) and the constraint that official API credentials require emailing Club OS support, which explains why the browser path exists.

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 clauses earn their place by describing the guidance-then-browser workflow, but the trailing API paragraph is generic boilerplate about calendars, agreements, leads and KPIs that has nothing to do with locker assignments. The dated check note ('11 Nov 2026') reads as crawl residue rather than decision-relevant information.

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 scopes it to the user's own account. It does not say what happens when no guidance exists for a requested locker action or that context comes from the active browser session, which would complete the picture.

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?

Zero parameters with 100% schema coverage, so the schema baseline is 4. The description adds no parameter meaning because none exists, but it correctly implies the tool is stateless and takes no input.

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 the resource (locker assignments in Club OS) and, crucially, discloses the actual mechanic: 'Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from an executing tool, though the verb 'Manage' in the opening is generic and overlaps with dozens of club_os_manage_* siblings.

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 gives a clear two-step workflow: call this to get steps, then perform the action with the cotlet_browser_* tools in the user's Club OS Cloud Browser. It does not state when to prefer this over a sibling manager tool or what to do if the guidance doesn't cover the user's scenario, so it stops short of full routing guidance.

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