Skip to main content
Glama

zanda_open

Opens a Zanda page in your signed-in cloud browser so you can work with practice calendars, waitlists, forms, messages, and reports.

Instructions

Open a Zanda page in your signed-in Cloud Browser (default https://my.zandahealth.com) to work with practice calendars, waitlists, forms, messages and 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": "zanda_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://my.zandahealth.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does add real context: navigation happens inside a signed-in Cloud Browser session, which tells the agent authentication state is assumed. However, it does not say whether this replaces the current page or opens a new one, whether existing state is lost, or what happens on an invalid URL or expired session.

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?

One sentence with the action and target front-loaded, followed by the domain scope. No filler or redundant phrasing; every clause adds something an agent can use.

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 no-argument navigation tool with no output schema and no annotations, the description covers purpose and default destination adequately. It stops short of explaining what the agent gets back after opening a page or how to proceed with the sibling interaction tools, which leaves a real gap for a browser-control workflow.

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% for the single optional url parameter, so the schema already documents the type and default. The description restates the default https://my.zandahealth.com but adds no syntax guidance (path format, query strings, relative vs absolute URLs), so the baseline of 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 names a specific verb and resource — 'Open a Zanda page in your signed-in Cloud Browser' — and scopes the tool to practice calendars, waitlists, forms, messages and reports. It is distinguishable from siblings like zanda_click and zanda_type, which imply in-page interaction rather than navigation, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the entry point for navigating to a page before interacting with it, and 'signed-in Cloud Browser' hints at a prerequisite session. There is no explicit when-to-use, when-not-to-use, or alternative named among zanda_click, zanda_guide, or zanda_read.

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