Skip to main content
Glama

extrabat_read

Reads the current Extrabat page, returning its text and numbered buttons, links, and fields; optionally limit reading to a specific element for targeted inspection.

Instructions

Read the current Extrabat 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": "extrabat_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

With no annotations, the description carries the full burden. It usefully discloses the key behavioral trait that interactive elements are returned as numbered items, which is what enables later click/type calls, but it says nothing about behavior when no page is open, truncation of large pages, or what happens with the element scoping.

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 that names the resource first and then the payload. No filler, hedging, or redundant restatement of the tool name.

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-parameter read tool with no output schema and full schema coverage, the description covers what is returned and how elements are identified. The main remaining gap is the unstated prerequisite that a page must be open, which would matter for correct invocation.

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?

The single parameter has 100% schema description coverage ("Read only inside this element"), so the baseline is 3. The description never mentions the element argument, so it adds no meaning beyond the schema, though the "numbered" reference loosely connects to the element-index concept.

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 concrete verb and resource ("Read the current Extrabat page") and enumerates what is returned: text, numbered buttons, links and fields. That distinguishes it from the write-oriented siblings (extrabat_click, extrabat_type) without naming them, though it never explicitly contrasts with any sibling.

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 ... page" hints that a page must already be open (via extrabat_open) before reading. There is no explicit statement of when to use this versus extrabat_status or extrabat_guide, and no stated preconditions or exclusions.

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