Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_click

Clicks a numbered element on the current HERO Software page, using the element number from the last page read to interact with the interface.

Instructions

Click a numbered element on the current HERO Software page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "hero_software_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and for an interactive action it does very little. It doesn't say whether the click navigates, mutates state, invalidates previously read element numbers, or what happens if the number is stale or out of range.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler. Its brevity edges toward under-specification, but nothing present is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a browser-state-mutating action with no annotations and no output schema, the description omits essential context: the prior-read requirement, post-click effects, and error behavior. An agent has to infer the operational contract.

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 schema already explains the single parameter as "Element number from the last read." The description only echoes "numbered element" without adding format, range, or staleness guidance beyond that.

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?

A specific verb ("Click") applied to a specific resource ("a numbered element on the current HERO Software page"). It is reasonably distinguishable from siblings like hero_software_read and hero_software_type, though the notion of a "numbered element" is only cashed out in the schema.

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: the word "current" hints that a page must already be open, and element numbers must come from a prior read. It never states the prerequisite workflow (read before click) or when to prefer alternatives such as the type tool.

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