Skip to main content
Glama

zanda_guide

Call this first to get guidance on navigating Zanda screens, the sign-in link, and where to handle practice calendars, waitlists, forms, messages, and reports for a given task.

Instructions

How to work in Zanda (practice calendars, waitlists, forms, messages and 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": "zanda_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Zanda, 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 supplied, so the description carries the full disclosure burden. It does reveal the content an agent can expect back (screens, sign-in link, guidance across the listed modules), which goes beyond the structured data on a tool with no annotations. However, it never states that the tool is read-only, what form the guidance takes (static instructions vs. contextual answer keyed to the task parameter), or how it relates to the task argument.

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 sentences, front-loaded with the substantive content and closed with the directive 'Call this first.' Nothing is wasted. The only weakness is that it is terse to the point of leaving the reader to infer whether the response is a static guide or a task-aware answer.

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 one-parameter, no-annotation, no-output-schema guide tool this is close to adequate: scope of coverage and the entry-point instruction are both present. What is missing is whether the output is fixed documentation or tailored to the 'task' input, which is the single ambiguity an agent would actually hit.

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% for the single 'task' parameter, so the schema already defines it as 'What you want done in Zanda, in your words.' The description adds no meaning about how that free-text value is interpreted or how specific it should be. Baseline 3 applies when the schema does the documentation work.

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 resource scope: guidance on working in Zanda, enumerated as practice calendars, waitlists, forms, messages and reports, plus screens and the sign-in link. That is more than a restatement of the name 'zanda_guide' and lets an agent tell this apart from action siblings like zanda_click or zanda_read. It stops short of 5 because the operative verb is implied ('how to work') rather than stated as a returned artifact.

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' is an explicit usage instruction that fixes this tool's position in a sequence relative to the sibling tools. It does not name an alternative or state when-not to use it, which keeps it below 5, but for an entry-point guide the timing guidance is unambiguous.

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