Skip to main content
Glama
clubready-mcp

clubready-mcp

clubready_click

Clicks a numbered element on the current ClubReady page using the element number from the last read, enabling navigation or selection after reviewing page content.

Instructions

Click a numbered element on the current ClubReady page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "clubready_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says nothing about what the click does beyond the literal action: whether it navigates, submits a form, mutates data, is repeatable, or what happens if the element number is stale after a page change. For an action tool with zero annotation coverage this is a meaningful gap.

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?

One front-loaded sentence with no redundant phrasing. It is efficient, though the extreme brevity is under-specification rather than economy of expression for a stateful action tool.

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?

The tool is simple (one integer parameter, no output schema needed), and the schema fully documents the input. However, for a page-mutating click with no annotations, an agent still lacks information about side effects, post-click page state, and stale-element handling, leaving the definition only minimally complete.

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% and the single parameter is fully documented ('Element number from the last read', minimum 1). The description's 'numbered element' adds no syntax or validation detail beyond the schema, so it sits at the baseline.

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 a concrete verb (click) and a concrete target (a numbered element on the current ClubReady page), which is distinguishable from read/type/open/close siblings by the action performed. It stops short of explicitly naming how it pairs with the read tool that produces the numbering.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'current ClubReady page' signals this operates on already-loaded state, and the schema hints the element number comes 'from the last read.' There is no explicit statement of when to prefer this over clubready_type or clubready_open, nor any stated prerequisite or failure mode.

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