Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_guide

Get guidance on navigating HERO Software screens and sign-in, then complete projects, quotes, invoices, and appointments with clear step-by-step instructions.

Instructions

How to work in HERO Software (trade business projects, quotes, invoices and appointments): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in HERO Software, in your words.

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. It does signal that this is a safe informational/orientation call and that it should precede other calls, but it never states that it is read-only, whether it changes any state, or in what form the screens and sign-in link come back.

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?

Two short clauses with no filler; the covered domains are packed parenthetically and the routing instruction lands early enough to be seen. The trailing 'Call this first' could have been front-loaded for maximum effect, which keeps it just under top marks.

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 one-optional-parameter orientation tool with no output schema, the description covers what the tool contains, which workflow areas it addresses, and when it should be invoked. Only the return shape and the read-only nature are left unstated, which is a modest gap for a low-complexity tool.

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?

There is a single optional parameter and the schema describes it fully ('What you want done in HERO Software, in your words'), so the schema does the heavy lifting. The description adds no guidance on how to phrase the task or what detail helps, so it is at the baseline level rather than enriching the parameter.

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 states the resource (a guide to working in HERO Software) and enumerates the domains it covers — trade business projects, quotes, invoices, appointments — plus screens and the sign-in link. It does not use a crisp verb like 'returns' or 'explains', but the scope is clear enough to distinguish it from the action-oriented siblings (click, open, read, type).

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 imperative 'Call this first' gives an explicit ordering rule that no sibling provides, which is genuinely useful routing guidance. It stops short of saying when NOT to use it or naming a specific alternative, so it is clear context rather than a full when/when-not/alternatives statement.

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