Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_close

Close the HERO Software browser session when work is done to stop credits from running.

Instructions

Close the HERO Software browser session when the work is done, so credits stop running.

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_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/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, and it does disclose the key consequence: the session ends and credit consumption stops. It says nothing about what happens to unsaved in-page state, whether the call is idempotent when no session is open, or what a failure looks like, which are the details an agent most needs before firing a terminating action.

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, no padding, and the action plus its motivation are both front-loaded. Every clause earns its place and nothing is restated from the schema or title.

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-parameter, no-output-schema tool this is close to sufficient: the agent knows what it does and why it matters. The remaining gap is the post-close state and idempotency behavior, which matters because this is a destructive-adjacent action with no annotations to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless action by describing the session as the only operand.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (close the HERO Software browser session) and adds a rationale (so credits stop running). That framing clearly separates it from siblings such as hero_software_open or hero_software_status, which begin or inspect a session rather than end one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is explicit: call this when the work is done. The implied counterpart is hero_software_open, but the description never names it or states an exclusion (for example, that it is safe to call on an already-closed session), so the routing guidance is clear but not fully closed.

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