Skip to main content
Glama

zenoti_guide

Call this first to learn Zenoti's screens and sign-in link so you can read appointments, draft guest replies, and review front desk reports.

Instructions

How to work in Zenoti (read appointments, draft guest replies and review front desk reports): 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": "zenoti_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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, and it never states that this is a side-effect-free read, whether the sign-in link is static, or whether authentication is required first. It implies a non-destructive informational tool but does not disclose it.

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?

Two compact fragments with the action instruction front-loaded and no filler. The parenthetical capability list is dense but earns its place by signaling scope.

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 one-parameter, no-annotation, no-output-schema guide tool, the description covers what it is, what it contains, and when to call it. The remaining gap is not describing the returned guidance format, which is mildly consequential given there is no output schema.

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 single 'task' parameter is documented in the schema, so the baseline applies. The description adds no meaning about how the free-text task is interpreted or what granularity of task description works best.

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?

Identifies itself as an orientation/guide tool and enumerates what it covers (screens, sign-in link, plus the tasks read appointments, draft guest replies, review front desk reports), which separates it from the action siblings like zenoti_click and zenoti_read. It stops short of saying what it actually returns (instructions vs. a URL), so it is clear but not fully precise.

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?

'Call this first' gives explicit sequencing guidance that no sibling name could supply on its own. It does not state when to skip it or when a sibling is preferable, but for an orientation tool the primary guidance is present.

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