Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_read

Reads the current HERO Software page, including text and numbered buttons, links, and fields, so an AI agent can inspect on-screen content and target elements.

Instructions

Read the current HERO Software 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": "hero_software_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 burden. It does disclose useful behaviour about the output shape — the page is returned as text with numbered interactive elements, which explains how the sibling click/type tools address targets — but it omits prerequisites (must a page be open?), error behaviour, and whether long pages are truncated.

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 verb and target, then the payoff (what content is returned). Nothing superfluous and no burying of the key scope.

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 single optional-parameter read tool with no output schema and no annotations, the description covers the core (what the page read yields) but leaves the 'element' scoping mechanism and any precondition for calling it unexplained. Adequate, with a clear remaining 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% with a single optional 'element' parameter whose description ('Read only inside this element.') is already documented in the schema. The prose adds no meaning about the numbering scheme used for 'element' or how it relates to the numbered buttons it mentions, so baseline 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?

States a specific verb ('read') applied to a specific resource ('the current HERO Software page') and enumerates what comes back: text plus numbered buttons, links and fields. That return-content detail implicitly separates it from mutation siblings like hero_software_click and hero_software_type, though no sibling is named.

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 — an agent can infer this is the tool to call to inspect a page before acting on it. There is no explicit when-to-use statement, no mention of an alternative (e.g. hero_software_status or hero_software_guide) and no exclusion of when not to use it.

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