Skip to main content
Glama
clubready-mcp

clubready-mcp

clubready_guide

Explains how to navigate ClubReady screens, manage customer profiles and memberships, handle club operations, and find the sign-in link so you can start tasks correctly.

Instructions

How to work in ClubReady (manage customer profiles, memberships and club operations): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in ClubReady, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully states that the tool returns guidance on screens and a sign-in link and should be called first, but it does not explain authentication needs, response shape, or whether the output is static or dynamic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is two tight sentences with no wasted wording. The content scope and the imperative 'Call this first' are front-loaded for quick agent use.

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 simple one-parameter guide tool, the description is largely complete: it says what the guide contains and when to invoke it. It could do slightly more to explain what calling it returns, but its scope is small enough that this is a minor gap.

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?

Schema description coverage is 100%, so the optional 'task' parameter is already defined as 'What you want done in ClubReady, in your words.' The description adds no further meaning about how that task shapes the returned guidance.

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 clearly identifies this as a ClubReady orientation/help resource covering screens and the sign-in link. It is distinguishable from the action-oriented siblings by its 'Call this first' framing, though it does not explicitly name any sibling.

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?

The phrase 'Call this first' gives clear and actionable when-to-use guidance before performing ClubReady work. It does not describe when not to use it or name alternative tools, 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.