Skip to main content
Glama

Club OS by Cotlet

View the calendar in Club OS

club_os_view_the_calendar
Read-onlyIdempotent

View the calendar 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_view_the_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/no-open-world, and the description adds real value beyond them by stating it "opens nothing by itself" — clarifying that despite the name, no calendar data is fetched or mutated. The official-API limitation (email support for credentials, with a check date) is exactly the kind of blocker an agent would otherwise waste a turn discovering.

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 purpose, then the return format, then the follow-on action, then the API caveat — a sensible order for an agent deciding whether to call it. It runs three dense sentences; the API note is slightly tangential but earns its place as a dead-end warning.

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 tool with no output schema, the definition covers what it returns (step-by-step screens/buttons/fields), what it does not do (opens nothing), and how to complete the underlying task. Nothing essential is missing, though one sample of the returned instruction shape would make it fully self-contained.

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 for the description to disambiguate; baseline for a no-param tool applies. The description adds no misleading parameter talk, keeping the contract clean.

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?

Opens with a specific verb and resource ("View the calendar in the user's own Club OS account") and scopes it to the account holder's calendar rather than a staff member's or an event-level action, which implicitly separates it from siblings like club_os_view_a_staff_member_s_calendar_from_user_search. It does not name an alternative explicitly, so differentiation is inferred from scope wording rather than stated.

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?

Clearly tells the agent what to do next: this tool returns step-by-step instructions and the actual action is performed with cotlet_browser_* tools in the user's Cloud Browser. The API caveat (credentials only via email to Club OS support) steers the agent away from an API path without needing a separate query. No explicit when-not-to-use case beyond that, but the routing is unambiguous.

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