Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_top_scorers

Retrieve a competition's FUSSBALL.DE top-scorer list with player, team, goals, and position; page results using limit and offset.

Instructions

Get the FUSSBALL.DE top scorers of a competition. Returns a page of a competition's top-scorer list with position, player, team and goals; page through it with limit (1 to 100, default 30) and offset. Tied scorers share a position. A competition without recorded scorers returns an empty list; cups and tournaments have no scorer list at all and return 404.

Input Schema

NameRequiredDescriptionDefault
limitNoScorers per call, 1 to 100, default 30
offsetNoNumber of scorers to skip, 0 to 1000, default 0
competition_idYesCompetition id from fussballde-competitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does well: it discloses the return fields (position, player, team, goals), explains that tied scorers share a position, and defines edge cases (empty list vs. 404 for cups/tournaments). It does not mention authentication or rate limits, but for a read-only data tool this is a strong disclosure.

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?

Two tightly written sentences plus a third for edge cases; the core purpose and paging mechanism are front-loaded with zero waste.

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, but the description explains the return fields and edge-case responses sufficiently for a read-only list tool. Only the pagination limits and 404 behavior are stated, which is enough to call it correctly.

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 coverage is 100%, so the schema already documents all three parameters. The description restates the limit/offset paging mechanism and defaults, adding no meaning beyond what the schema provides; baseline 3 is appropriate.

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: 'Get the FUSSBALL.DE top scorers of a competition.' It clearly describes what the tool returns, distinguishing it from generic competition listings, though it does not explicitly name the sibling `fussballde_national_top_scorers`.

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

Usage Guidelines3/5

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

Usage is implied by 'of a competition' and the note that cups/tournaments return 404, which tells the agent when not to use it. However, there is no explicit alternative tool suggested for national top scorers or cup statistics, leaving the agent to infer.

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