Skip to main content
Glama

zanda_status

Check that your Cotlet.dev account, credits, and Zanda connection are ready before using practice-management tools.

Instructions

Check that your Cotlet.dev account and Zanda are ready: account, credits and Zanda connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/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. "Check" signals a read-only operation and the text reveals the scope of the checks and hints at authentication via "your Cotlet.dev account," but it says nothing about what happens on failure, whether anything is mutated, rate limits, or the shape of the result.

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 a colon-delimited list of exactly what is checked. Every element earns its place and nothing is padded.

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-parameter diagnostic tool with no output schema, the description covers the inputs (none) and the verification scope (account, credits, connection), which implicitly maps to three result items. It stops short of stating the return format or what to do when a check fails, which would be the remaining useful addition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the absence of parameters is fully consistent with the stated purpose of a readiness check.

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 gives a specific verb ("Check") and a specific target (account, credits, Zanda connection readiness), enumerating the three things verified. That distinguishes it well from the sibling tools (click, close, guide, open, read, type), which are all UI interaction verbs, though it never explicitly names them.

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 wording "Check that ... are ready" implies a preflight/diagnostic use before interacting with Zanda, but there is no explicit when-to-use statement, no when-not-to-use, and no mention of alternatives for troubleshooting. The agent must infer the usage context.

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