Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_open

Open a HERO Software page in your signed-in Cloud Browser to manage trade business projects, quotes, invoices and appointments.

Instructions

Open a HERO Software page in your signed-in Cloud Browser (default https://login.hero-software.de) to work with trade business projects, quotes, invoices and appointments.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://login.hero-software.de

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?

With no annotations, the description must carry behavioral weight, and it does disclose the key precondition of a 'signed-in Cloud Browser'. However it omits what happens on failure (not signed in), whether the current page is replaced or a new tab/context is used, and any rate or session constraints on a navigation tool that controls a shared browser session.

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?

A single compact sentence with the action front-loaded and the default URL parenthesized rather than given its own sentence. No wasted wording.

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?

No output schema exists, so the description would ideally say what the agent gets back after opening a page (e.g., page content, confirmation, resulting URL) and how to recover from an unauthenticated state. For a one-parameter navigation tool the current text is passable but leaves that operational 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% and there is a single optional url parameter already fully documented, so the baseline is 3. The description repeats the default URL that the schema already supplies, adding no new syntax or format guidance.

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 ('Open') and resource ('a HERO Software page in your signed-in Cloud Browser'), and names the domain area served (projects, quotes, invoices, appointments). It is distinguishable from siblings like hero_software_read or hero_software_click, though it never explicitly contrasts itself with them.

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: the agent must infer that this is the entry/navigation step before reading or clicking. There are no explicit when-to-use or when-not-to-use conditions and no named alternatives among the siblings such as hero_software_read.

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