Skip to main content
Glama

netgrind_read

Reads the current NetGrind page to return its text plus numbered buttons, links, and fields, optionally limited to a specific element for targeted inspection.

Instructions

Read the current NetGrind 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": "netgrind_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 supplied, the description carries the full disclosure burden. It does describe the payload (text plus numbered controls), which implies a non-mutating inspection, but it never states that it is read-only, what happens if no page is open, or how large pages are truncated/paginated.

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 colon-structured sentence that front-loads the action and then lists the returned content; there is no filler or repetition.

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-required-parameter inspection tool with a fully documented schema and no output schema, the description covers purpose and returned content adequately; only error/empty-state behavior is left implicit.

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 sole optional 'element' parameter is documented in the schema as scoping the read to a subtree, so the baseline of 3 applies. The description adds nothing about scoping or how element indices are obtained.

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?

States a specific verb and resource ("Read the current NetGrind page") and enumerates what it surfaces: text, numbered buttons, links and fields. That enumeration makes it distinguishable from siblings like netgrind_click and netgrind_type, though it never 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?

Usage is only implied: the phrase "numbered buttons" hints that this is the observation step preceding a click or type, but the description never says when to call it versus netgrind_status or netgrind_guide, nor any preconditions such as a page already being open.

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