Skip to main content
Glama

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Cohort summary (AT + DE)

get_cohort_summary
Read-onlyIdempotent

Aggregate statistics for a cohort of companies, per country. Read-only.

    Parameters:
    - dimension (required): "gkl" (UGB size class, AT only), "bundesland", or
      "legal_form" (alias size_gkl -> gkl).
    - value (required): the cohort value (e.g. bundesland "Wien", legal_form "GmbH").
    - country (optional, default "all"): "AT" | "DE" | "all".

    Returns {countries, dimension, value, per_country, notices}. ``bundesland`` and
    ``legal_form`` fan out to every supporting country; ``gkl`` is Austrian-only (no German
    size-class facet) and excludes DE with a notice. Each country's own cohort payload sits
    under ``per_country`` (the registers aggregate different metrics, so they are reported
    side by side, not force-merged). For one company use get_company_details; for a filtered
    list use search_companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
countryNoall
dimensionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description is not burdened with that. It adds genuine non-obvious behavior: 'gkl' excludes DE with a notice, and per-country payloads are reported side by side rather than force-merged because registers aggregate different metrics. It does not cover auth requirements or performance/rate characteristics, so not a full 5.

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?

Front-loads the one-line purpose plus read-only status, then a parameter block, then return/fan-out semantics. Because schema coverage is 0%, the parameter listing is necessary rather than redundant, and every sentence carries routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param aggregate tool with an output schema present, the description supplies everything needed: the parameter contract, the country/dimension interaction rules, the notice mechanism, and hand-offs to the two sibling tools. Return-value explanation is kept brief because the output schema covers structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it documents all three parameters, marks required vs optional, gives the default for country, enumerates valid dimension values, supplies example values ('Wien', 'GmbH'), and discloses the 'size_gkl -> gkl' alias that appears nowhere in the schema.

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 verb+resource with scope: aggregate statistics for a cohort of companies, broken down per country. It explicitly contrasts itself with get_company_details (single company) and search_companies (filtered list), so an agent can place it among siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the two nearest alternatives and the exact condition that selects each: 'For one company use get_company_details; for a filtered list use search_companies.' It also explains when a dimension fans out to multiple countries versus when it is Austrian-only, which is precisely the routing decision an agent must make.

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