Skip to main content
Glama
Sign In

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Describe fields & capabilities

describe_fields
Read-onlyIdempotent

Beispiel: „Welche Felder und Filter gibt es?“

Schema self-description: the unified id scheme, which filters exist, which countries support which capability, and each country's own field catalog. Read-only.

    Parameters:
    - country (optional, default "all"): "AT" | "DE" | "all" - whose field catalogs to
      include.

    Returns {id_scheme, capabilities, countries, countries_unavailable}. ``id_scheme``
    documents the unified company_id ("AT:123456a", "DE:D2601_HRB135076"; bare national
    ids are accepted, responses always return the prefixed form). ``capabilities`` is
    the per-country capability matrix including each country's supported unified
    filters - a filter absent for a country is applied to the others and reported in a
    notice, never silently dropped. ``countries`` carries each backend's own
    describe_fields payload (code tables, null rules, tool tiers). Call once up front
    when unsure which filter or tool to use; it returns no company data itself.

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

Input Schema

NameRequiredDescriptionDefault
countryNoall

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is covered. The description adds genuine behavior beyond that: a filter unsupported for one country is applied to the others and surfaced in a notice rather than silently dropped. It also documents bare-id acceptance and prefixed-id returns.

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?

Core purpose and the param are stated early, and the Returns section is scoped to the non-obvious semantics rather than a field dump. The opening German example sentence is a slightly awkward lead-in but does double as a usage cue; the rest earns its place.

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 an output schema present, the description needn't enumerate return values, yet it usefully explains the id_scheme examples and the cross-country filter fallback that the schema cannot convey. Combined with the one optional parameter being fully described, an agent has what it needs to call it correctly.

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?

Schema coverage is 0% and the schema even lacks an enum, so the description must carry the load — it supplies the accepted values 'AT' | 'DE' | 'all', the default, and the meaning ('whose field catalogs to include'). It stops short of describing what happens for countries outside AT/DE.

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?

States a specific resource and scope: the unified id scheme, available filters, per-country capability matrix, and each country's field catalog. It explicitly separates itself from data-returning siblings with 'it returns no company data itself', so an agent can tell it apart from search_companies or get_company_details.

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?

Gives a clear trigger: 'Call once up front when unsure which filter or tool to use', and notes it returns no company data, implying it is a discovery step. No specific sibling alternative is named for the case where you already know the filter, but the guidance is actionable.

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

All Handelsregister toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources