Skip to main content
Glama

zenoti_open

Opens a Zenoti page in your signed-in Cloud Browser so you can review appointments, draft guest replies, and check front desk reports.

Instructions

Open a Zenoti page in your signed-in Cloud Browser (default https://www.zenoti.com) to work with read appointments, draft guest replies and review front desk reports.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.zenoti.com

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?

No annotations are supplied, so the description carries the full disclosure burden. It adds one genuinely useful behavioral fact: the operation acts on an already 'signed-in Cloud Browser', which tells the agent authentication is assumed rather than performed. Beyond that it is silent on navigation semantics (new tab vs. current tab, what happens if a page is already open) and on what is returned, which matters for a browser-control tool with zero annotation coverage.

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 front-loaded sentence with the action first and the default URL and use cases following; no filler or redundancy. The trailing list of example tasks is slightly loose but still earns its place as usage context.

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 simple one-optional-parameter tool with no output schema, the description covers what it does, where it operates, and the default target. The main residual gap is return behavior and tab/session semantics, which is acceptable but not fully closed.

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 schema already documents the url parameter including its default. The description merely repeats the same default (https://www.zenoti.com) and adds no format, path, or relative-vs-absolute URL guidance, so it sits at the baseline for a fully documented single parameter.

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?

States a specific verb (Open) and resource (a Zenoti page) plus the environment (signed-in Cloud Browser) and the default target URL, which is concrete and unambiguous. It does not explicitly contrast itself with siblings like zenoti_read or zenoti_status, so it falls short of a 5.

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?

The clause 'to work with read appointments, draft guest replies and review front desk reports' implies the situations where opening a page is the right first step. However, it never states prerequisites (e.g. whether a session must already exist) nor names an alternative tool or a when-not-to-use condition, leaving the agent to infer the sequencing.

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