Skip to main content
Glama

crexi_click

Click a numbered element on the current Crexi page to interact with listings, controls, and navigation using the element number from the last read.

Instructions

Click a numbered element on the current Crexi 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": "crexi_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.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole behavioral burden. It never says what a click does beyond the act itself — whether it navigates, submits a form, mutates state, closes a modal, or fails on an out-of-range index. For a browser-mutating tool with zero annotation coverage, this leaves the risk profile and side effects undisclosed.

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?

A single tight sentence with the action front-loaded and no filler. It is not padded, though the brevity comes at the cost of the behavioral detail noted elsewhere rather than from disciplined prioritization.

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

Completeness2/5

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

With no annotations and no output schema, the definition must stand on its own, and it omits what happens after the click, whether the page or element numbering changes, and how failures surface. For an interaction tool where post-click state matters to the next step, this is under-specified.

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%, with the single parameter documented as 'Element number from the last read', so the schema already does the explanatory work. The description's 'numbered element' phrase reinforces the tie to a prior read but adds no new syntax, bounds, or error semantics beyond the schema. Baseline 3 applies.

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 gives a specific verb and resource: 'Click a numbered element on the current Crexi page.' Combined with 'number from the last read' in the schema, an agent can tell this is the page-interaction tool, distinct from crexi_type or crexi_open. It stops short of explicitly naming which sibling to use for typing or navigation, so it is clear but not fully differentiated.

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 'numbered element' plus the schema's 'Element number from the last read' hints that crexi_read must run first and that numbers are ephemeral. There is no explicit when-to-use statement, no mention of when to prefer crexi_type or crexi_open, and no warning about stale element numbers after a prior action.

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