Skip to main content
Glama

zenoti_click

Clicks a numbered element on the current Zenoti page using the element number from the last read.

Instructions

Click a numbered element on the current Zenoti 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": "zenoti_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.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only states the action without disclosing behavioral traits. It does not explain what happens after clicking (navigation, form submission, state change), whether the action is reversible, what permissions are needed, or how it interacts with page state. This is a significant gap for a mutating interaction.

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 description is a single, front-loaded sentence that states the verb and target with zero waste. It is appropriately sized for a simple click 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?

For a simple click tool with no annotations and no output schema, the description is adequate but incomplete. It omits behavioral details such as what clicking does, whether any feedback is returned, and how the numbered elements are obtained (though the schema hints at a prior read).

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 in the schema as 'Element number from the last read.' The description adds no meaning beyond that, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific verb (Click) and resource (numbered element on the current Zenoti page), making the action clear. It does not explicitly differentiate from siblings like zenoti_type or zenoti_read, but the verb itself is distinct enough that an agent can infer the tool's purpose without opening the schema.

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 implied: the element number comes from a prior read (as the schema notes), so the tool is meant to be used after zenoti_read. However, there is no explicit guidance on when to use click versus other interaction tools, nor are there exclusions or listed prerequisites.

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