Skip to main content
Glama

hapana_read

Read the current Hapana page to capture its text and numbered buttons, links, and fields, optionally scoped to a single element for targeted inspection.

Instructions

Read the current Hapana 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": "hapana_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about side effects, whether the returned element numbers are the indices consumed by hapana_click/hapana_type, or whether output is truncated. Only the phrase "current" hints that this reflects live page state.

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 action and immediately enumerating the payload. No filler, nothing repeated from structured fields.

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 read tool this covers the what, and with no output schema the description is the only place return shape could be explained. It names content categories but not the numbering scheme that appears to connect it to the click and type tools, leaving that integration gap.

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%, so the single optional 'element' parameter is already documented with a scope meaning ("Read only inside this element"). The description adds nothing beyond the schema here, 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 definition names a specific verb and resource ("Read the current Hapana page") and enumerates what is returned: text, numbered buttons, links and fields. That scope naturally separates it from hapana_click and hapana_type, though no sibling is named to make the separation explicit.

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?

Use is only implied: inspecting the page is the obvious prerequisite for acting on it. There is no statement of when to call this read versus hapana_status, no exclusions, and no note on re-reading after an action.

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