Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_position_history

Retrieve every team's table position after each played matchday in a FUSSBALL.DE competition to track league position history (Fieberkurve) as ordered lists per team.

Instructions

Get the FUSSBALL.DE fever curve of a competition. Returns every team's table position after each played matchday of a competition (the site's Fieberkurve), as one ordered list of positions per team. Position 1 is the leader; the list index is the matchday.

Input Schema

NameRequiredDescriptionDefault
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 the burden and does well: it discloses the return shape (one ordered list of positions per team), the indexing convention (list index = matchday), and the orientation (position 1 is the leader). It omits any handling of unplayed matchdays or gaps in the series, so it is not fully complete.

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 short sentences with zero filler; the concept is named first, then the payload, then the indexing convention the reader needs to interpret it.

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?

With no output schema, the description supplies the essential return semantics an agent needs to interpret the result. Minor gaps remain around ordering guarantees across teams and behavior for matchdays not yet played.

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?

Only one parameter, and schema coverage is 100% with a description pointing at fussballde_competitions. The description adds no further detail on the id's format or accepted values, so the schema does all the parameter work.

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 fever curve of a competition') and explains the payload — every team's table position per played matchday. It is clear on its own, but it never distinguishes itself from the sibling fussballde_table, which an agent would plausibly confuse with this historical series.

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 only implied by the word 'history' and 'after each played matchday'; there is no explicit statement of when to pick this over fussballde_table or fussballde_matchday, nor any prerequisite about where competition_id comes from beyond the schema.

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