Skip to main content
Glama

eRechio – E-Rechnungen prüfen

Zustand der eRechio API

status
Read-onlyIdempotent

Zustand, Version und Regelstand der eRechio API (wie GET /v1/status). Ohne Schlüssel, zählt nicht im Kontingent.

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": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing two operationally useful facts: it needs no API key ('Ohne Schlüssel') and does not consume quota ('zählt nicht im Kontingent'). Annotations already declare readOnly/idempotent/non-destructive, so the added auth and rate-limit context is the real value here; it stops short of describing the response shape.

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 resource, the fields returned, the endpoint analogue, and the auth/quota caveat front-loaded. No filler and nothing that repeats the annotations verbatim.

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?

With no output schema, the description correctly enumerates the returned content (status, version, rule state), which is what an agent needs. Zero-parameter tools need little more; only the exact response format is left unspecified.

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 no parameter meaning to convey and the baseline of 4 applies. Nothing in the description misrepresents the empty input schema.

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?

Names the specific resource and what it returns: 'Zustand, Version und Regelstand der eRechio API', and anchors it to a known endpoint (GET /v1/status). An agent can tell this is an API health/version probe, clearly distinct from the invoice-check sibling, though the description never names that sibling explicitly.

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 by the endpoint analogy: an agent infers 'call this to check API health/version'. There is no explicit statement of when to use it versus other tools, nor any preconditions, but for a zero-parameter probe the implied usage is fairly unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources