Skip to main content
Glama
clubready-mcp

clubready-mcp

clubready_open

Open a ClubReady page in your signed-in Cloud Browser to manage customer profiles, memberships, and club operations.

Instructions

Open a ClubReady page in your signed-in Cloud Browser (default https://app.clubready.com) to work with manage customer profiles, memberships and club operations.

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": "clubready_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.clubready.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It usefully states that the browser is signed-in and provides the default URL, but it omits what opening a page does to existing pages, error handling, and whether session state is preserved.

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 definition is a single front-loaded sentence with no superfluous clauses. The phrase 'to work with manage customer profiles' is slightly awkward, but the overall structure remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter navigation tool this is adequate, but with no annotations or output schema the description should be more explicit about session behavior and when to use it. It covers the default URL and signed-in context while leaving key operational gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter is already fully described in the schema, including its default value. The description repeats the default URL and contextualizes it as a ClubReady page, but adds no format or constraint detail beyond what the schema already provides.

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 uses a specific verb, 'Open', and resource, 'ClubReady page', and scopes it to the signed-in Cloud Browser. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as clubready_click or clubready_read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives broad business context around customer profiles, memberships, and club operations, but it does not state when to use this tool instead of clubready_click, clubready_read, clubready_status, or clubready_close. There are no exclusions or explicit prerequisites beyond the implied signed-in browser.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.