Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

fussballde_player_search

Search FUSSBALL.DE players by first or last name, optionally filter by postcode or place, and retrieve IDs, birth dates, teams, and team types. Use paging to review total hits and results.

Instructions

Search FUSSBALL.DE players by name. Searches players registered on FUSSBALL.DE by first and/or last name, optionally narrowed by postcode or place, and returns each player's id, name, birth date, team and team type. The first page reports the total hit count; page with limit (1 to 100, default 20) and offset, and final marks the last page. At least one of first_name and last_name is required. No match is a valid empty result.

Input Schema

NameRequiredDescriptionDefault
limitNoPlayers per call, 1 to 100, default 20
placeNoPostcode or place name to narrow the result; cannot be used alone
offsetNoNumber of players to skip, 0 to 2000, default 0
last_nameNoLast name; first_name or last_name is required
first_nameNoFirst name; first_name or last_name is required

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/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 does well: it discloses pagination semantics (limit 1-100 default 20, offset), that `total` only appears on the first page, that `final` marks the last page, and that an empty result is legitimate. It says nothing about result ordering or rate limits, which remain gaps.

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 sentences that each earn their place: scope first, result shape and pagination second, parameter constraints and empty-result behavior last. No filler or restating of the tool name.

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?

No output schema exists, and the description compensates by listing the returned fields plus the pagination envelope (total/limit/offset/final). For a five-parameter search tool that is close to complete; matching behavior and result ordering are the only unaddressed details.

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 already 100%, but the description adds value the schema cannot express: the schema declares `required: []`, while the description states the at-least-one-of-first_name/last_name rule and the "place cannot be used alone" dependency. It adds no ranking or matching semantics (exact vs. partial name match), which keeps it below 5.

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?

States a specific verb and resource ("Search FUSSBALL.DE players by name") and enumerates the returned fields (id, name, birth date, team, team type). It does not name the obvious sibling `fussballde_player` for detail-by-id, so an agent must infer that from "returns each player's id".

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 concrete preconditions: at least one of `first_name`/`last_name` is required, `place` cannot be used alone, and no match is a valid empty result rather than an error. It lacks an explicit "for full player profile use fussballde_player instead" routing statement, so alternatives are only implied.

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