Skip to main content
Glama

ontraccr_read

Read the current Ontraccr page to get its text and numbered buttons, links, and fields; optionally restrict the read to one element.

Instructions

Read the current Ontraccr 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": "ontraccr_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does add real behavioral value: it reveals that interactive elements come back 'numbered', which is the key affordance the agent needs to reference targets for ontraccr_click. It omits failure modes (no page loaded), output size/truncation, and whether reading has side effects, which keeps it below a 5.

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 ending with the concrete return contents. Nothing is wasted and nothing is buried.

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 single-optional-parameter read tool with no output schema and no annotations, the description covers what it does and what comes back. The remaining gap is that it never explains the element-scoping option or the relationship to the click tool, which is the main thing an agent needs to act on the numbered output.

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% and the single 'element' parameter is already documented as 'Read only inside this element', so the schema does the work. The description adds no scoping semantics of its own — notably it never states that omitting the parameter reads the whole page, which would have been the one useful addition.

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 names a specific verb and resource ('Read the current Ontraccr page') and enumerates what is returned: text, numbered buttons, links, and fields. It is distinguishable from the click/type/open siblings by implication, though it never names an alternative to contrast against.

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 by the word 'current' — the agent can infer this reads whatever page is presently loaded rather than an arbitrary URL, but there is no explicit statement of when to call this versus ontraccr_status, ontraccr_guide, or ontraccr_open, and no when-not guidance.

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