Skip to main content
Glama

zenoti_read

Read the current Zenoti page's text and numbered buttons, links, and fields, with an option to limit reading to one element so AI agents can inspect signed-in account content.

Instructions

Read the current Zenoti page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does disclose the return payload's shape (text plus numbered buttons, links, fields), which is the most useful behavioral fact here. It says nothing about output size, truncation, pagination, or whether the numbering is the same index space used by click/type, which are the real risks for this kind of tool.

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?

A single front-loaded sentence with no filler; the verb and target come first and the enumeration of returned content follows immediately.

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 zero-required-parameter read tool with no output schema and full schema coverage, the description tells the agent what it will get back, which is the main thing missing from structured data. Only the volume/truncation behavior and the linkage between the numbering and the click/type tools remain unexplained.

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 coverage is 100% and the only parameter, element, is already documented in-schema as "Read only inside this element." The description adds no scoping, format, or indexing detail beyond that, so the 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?

"Read the current Zenoti page" pairs a specific verb with a specific resource, and the colon list (text, numbered buttons, links, fields) tells the agent exactly what the observation yields. It is clearly the observation counterpart to zenoti_click/zenoti_type, though it never names those siblings explicitly.

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?

There is no statement of when to call this versus the alternatives (zenoti_status, zenoti_guide) and no sequencing advice such as re-reading after an action. A careful reader can infer it is the look-before-you-act tool, but the definition leaves that entirely to inference.

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