Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_news

List FUSSBALL.DE news by stream, Regionalliga league, or help category with paginated teasers; use returned article IDs to fetch full text.

Instructions

List FUSSBALL.DE news. Returns news teasers of one FUSSBALL.DE stream (all news, magazine, Regionalliga, federations, service, campaigns or help center) with title, category, publication date and time, and excerpt, paged with limit (1 to 50, default 10) and offset; final is true on the last page. Use regional_league or help_category to narrow the Regionalliga and help-center streams to one league or category. Use the article id with fussballde-news-article for the full text.

Input Schema

NameRequiredDescriptionDefault
limitNoArticles per call, 1 to 50, default 10
offsetNoNumber of articles to skip, 0 to 5000, default 0
streamNoNews stream, default all_news
help_categoryNoOnly help-center articles of one category (implies stream helpcenter)
regional_leagueNoOnly Regionalliga news of one league (implies stream regionalliga)

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 disclosure burden and clearly presents this as a listing operation returning teasers. It also explains pagination via limit and offset and states that final is true on the last page, though it omits auth, rate-limit, or error behavior.

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?

The description is front-loaded with the tool's purpose and return shape, then covers pagination, stream narrowing, and article follow-up. Every sentence contributes useful context without waste.

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?

There is no output schema, but the description explains the returned teaser fields, pagination, last-page signaling, stream options, and how to fetch full article text. That is complete enough for an agent to invoke the tool 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 description coverage is 100%, so all five parameters are already documented. The description repeats the paging behavior and the stream-narrowing use of regional_league and help_category but adds limited syntax or semantics beyond the schema.

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?

The description states a specific verb and resource: list FUSSBALL.DE news. It also names the stream scope and return fields, and distinguishes the tool from fussballde-news-article by pointing to the article id for full text.

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?

It explains how to narrow Regionalliga and help-center streams with regional_league or help_category, and says to use fussballde-news-article for full text. It does not explicitly compare this tool with fussballde_news_search, so the alternative-selection guidance is not complete.

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