Skip to main content
Glama
jkbngb

agentic-firmenbuch

by jkbngb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Describe available fields

describe_fields
Read-onlyIdempotent

Catalog every field the server can return by tool tier, including code tables and null rules, to help you pick the right tool and interpret its output.

Instructions

Catalog of every field the server can return, by tool tier (search card -> full profile -> full record), with code tables and availability/null rules. Read-only, no parameters.

    This describes the SCHEMA only (field names, types, code tables, null rules) so you can
    pick the right tool and interpret its output. It returns no company data itself; for that
    call search_companies (many) or get_company_details / get_full_record (one). Call this
    once up front when unsure what a field means or which tool to use.
    Human-readable version: https://www.agentic-firmenbuch.at/felder.html

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description nonetheless adds the meaningful fact that the tool returns schema metadata only and no company data, plus the tier structure (search card -> full profile -> full record). It does not discuss any rate limits or output structure beyond that, but with strong annotation coverage this is solid added context.

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?

The purpose and the schema-only constraint are front-loaded, and the alternative-routing sentence earns its place. The trailing documentation URL and the restated 'describes the SCHEMA only' phrasing add minor redundancy, keeping it just short of ideal.

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 parameterless, read-only catalog tool with an output schema present, the description covers everything an agent needs: what it returns (field names, types, code tables, null rules), what it does not return, when to call it, and where to get real data instead. Return-value explanation is correctly deferred to the output schema.

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?

Zero parameters, so the baseline is 4; the description explicitly confirms 'no parameters', which matches the empty schema and leaves no ambiguity about invocation.

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 and resource ('Catalog of every field the server can return') and immediately scopes it as schema-only with no company data, which cleanly separates it from the data-returning siblings it names (search_companies, get_company_details, get_full_record). An agent can distinguish it from all 17 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?

Gives an explicit trigger ('Call this once up front when unsure what a field means or which tool to use') and routes the agent to the correct alternatives for actual data, distinguishing the many-result tool from the single-result tools. When-not is implied by 'it returns no company data itself', which is sufficient to prevent misuse.

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

Deploy Server

Other Tools