Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

hero_software_status

Verifies your Cotlet.dev account, available credits, and HERO Software connection so you can confirm setup before using the integration.

Instructions

Check that your Cotlet.dev account and HERO Software are ready: account, credits and HERO Software connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 behavioral burden. It usefully discloses the three things being verified (account, credits, connection), which is real information beyond the name, but it says nothing about side effects, read-only nature, permissions, cost of the check, or what the result looks like.

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?

A single front-loaded sentence with no filler, though the phrasing is mildly awkward: 'account' appears twice and the colon-list structure reads like a compressed inventory rather than a clean statement.

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?

With no parameters and no output schema, the description should explain what a status verdict looks like (e.g., per-item ready/not-ready flags or error signals), since the agent must interpret the result. It lists the checks but not their outcomes, leaving a meaningful gap for a diagnostic tool.

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 the schema-vs-description gap is not applicable and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 uses a specific verb ('Check') and enumerates what is verified: account readiness, credits, and the HERO Software connection. It is clearly distinguishable from the UI-interaction siblings (click, close, open, type, read), 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: 'Check that ... are ready' suggests a preflight/verification step before other HERO Software operations, but there is no explicit statement of when to call it, when not to, or which sibling to use instead. An agent can infer intent but must guess the trigger condition.

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