Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_postal_codes

Look up German postcodes by place name or postcode prefix and return five-digit postal codes with city and district for match calendar location searches.

Instructions

Look up German postcodes by place name. Returns the German postcodes (with city and district) that FUSSBALL.DE's own location search suggests for a place name or postcode prefix. Use it to turn a place such as Dortmund into the five-digit postal_code that fussballde-match-calendar requires. No match is a valid empty list.

Input Schema

NameRequiredDescriptionDefault
qYesPlace name or postcode prefix, 2 to 40 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and mostly does: it discloses that results come from FUSSBALL.DE's own location search, that each result includes city and district, and that 'No match is a valid empty list' rather than an error — a genuinely important behavioral trait. It stops short of describing ordering, pagination, or any rate/permission constraints, which keeps it out of the top band.

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?

Three front-loaded sentences with no filler: what it does, what it returns, and how to use it. Nothing repeats the schema verbatim and every sentence carries information an agent needs.

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 one-parameter lookup with a 100%-documented schema and no output schema, the description supplies everything needed: purpose, input-to-output mapping (place name → five-digit postal_code), result contents (city, district), and empty-result semantics. No material gap remains for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100% and the single `q` parameter already documents the accepted forms and the 2–40 character bound, so the description's 'place name or postcode prefix' largely restates the schema. It adds no format, casing, or normalization guidance beyond that, so baseline 3 is appropriate.

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 ('Look up German postcodes by place name') and immediately scopes the output ('postcodes (with city and district) that FUSSBALL.DE's own location search suggests'). It also distinguishes itself from the geocoding-style siblings by anchoring to FUSSBALL.DE's own index, so an agent can tell it apart from the many other fussballde_* tools without opening the schema.

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 concrete when-to-use: 'Use it to turn a place such as Dortmund into the five-digit postal_code that fussballde-match-calendar requires', naming the downstream consumer and the required format. It does not add explicit exclusions (e.g., non-German places, or when another postal lookup would be preferable), so it stops just short of a full when/when-not guide.

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