Skip to main content
Glama

zanda_read

Reads the current Zanda page to extract visible text and numbered buttons, links, and fields; optionally limits reading to a specific element.

Instructions

Read the current Zanda page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

No annotations are supplied, so the description carries the full disclosure burden. It does communicate the output contract (text and numbered elements) and implies a side-effect-free read, but says nothing about whether element numbers stay stable between reads, whether long pages are truncated, or whether it waits for page load — all material for a snapshot tool feeding click/type siblings.

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, front-loaded with the verb and target, with zero filler. Nothing is redundant or buried.

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?

With no annotations and no output schema, the description must stand alone, and it does cover what is returned. It leaves out the operational details that matter most here — element-number stability, truncation limits, and when to prefer sibling tools — so it is adequate but not complete for a 6-tool browser suite.

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 single optional parameter `element` is already documented as "Read only inside this element." The description never mentions scoping to an element, so it adds no meaning beyond the schema; baseline 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 gives a specific verb ("Read") and resource ("the current Zanda page") and enumerates what comes back: text plus numbered buttons, links and fields. That return inventory implicitly separates it from action-oriented siblings like zanda_click and zanda_type, though no sibling is named 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: "current" hints that you call this to refresh page state and harvest element numbers before acting. There is no explicit when-to-use, when-not-to-use, or comparison against zanda_status or zanda_guide, so the agent must infer the workflow.

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