Skip to main content
Glama

ezee_optimus_read

Read the current eZee Optimus page to capture visible text plus numbered buttons, links, and fields; optionally limit reading to a specific element.

Instructions

Read the current eZee Optimus 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": "ezee_optimus_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?

No annotations are supplied, so the description carries the full behavioral burden. 'Read' implies a non-mutating operation and the description usefully discloses the returned contents, but it says nothing about whether state changes, what happens on a stale or closed page, or how the numbering scheme relates to click targets.

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 tightly written sentence, front-loaded with the action and resource, then the payload. Nothing is padded and nothing is redundant.

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?

Since there is no output schema, the description does the necessary work of describing what comes back (text, numbered buttons, links, fields). The remaining gap is that the numbering convention that presumably feeds ezee_optimus_click is never spelled out, and the element-scoping behavior is left entirely to the schema.

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 optional 'element' parameter is already documented as 'Read only inside this element.' The description adds no scoping semantics of its own, so the baseline 3 applies with the schema doing the work.

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 eZee Optimus page') and enumerates what the read yields: text plus numbered buttons, links and fields. That is enough to separate it from the action-oriented siblings like ezee_optimus_click and ezee_optimus_type, though it never explicitly states the contrast.

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' suggests it is called after ezee_optimus_open or a navigation, and that clicking should follow it. There is no explicit when-to-use, no prerequisite about having a page open, and no mention of ezee_optimus_status or ezee_optimus_guide as alternatives.

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