Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_news_search

Search FUSSBALL.DE editorial news or Profi-Newsflash by keyword to find relevant articles by title, category, date, and excerpt, with paging for controlled result review.

Instructions

Search FUSSBALL.DE news. Searches FUSSBALL.DE editorial news (news) or the Profi-Newsflash (pro_news) by keyword and returns teasers with title, category, date and excerpt. The first page (offset 0) also reports the total hit count; page with limit (1 to 50) and offset. No hits is a valid empty result.

Input Schema

NameRequiredDescriptionDefault
qYesSearch text, 2 to 80 characters
limitNoArticles per call, 1 to 50, default 10
offsetNoNumber of hits to skip, 0 to 10000, default 0
channelNoNews channel, default news

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden; it discloses the returned fields (title, category, date, excerpt), the special offset-0 total-hit-count behavior, and that zero hits is a valid empty result. It omits things like result ordering/relevance behavior and any auth or rate constraints, so not a 5.

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?

Four short sentences, front-loaded with the purpose, then channels, then return shape, then pagination/empty-result note. No filler or repetition; every sentence carries information.

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?

For a 4-parameter read tool with no annotations and no output schema, the description covers channels, return fields, pagination bounds, and empty-result semantics. Remaining gaps are minor (sort order, whether matching is literal substring vs. relevance-ranked), so 4 is appropriate.

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 100%, so baseline is 3, but the description adds genuinely new meaning: it explains what the channel enum values represent in domain terms and that offset 0 returns the total hit count. q and limit semantics are largely restated from the schema.

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 news') and clearly delineates the two channels it queries (editorial news vs. Profi-Newsflash), plus the return shape. It does not explicitly name the sibling tools it is not (e.g., fussballde_news, fussballde_news_article), so an agent must infer the split from those names, keeping it at 4 rather than 5.

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 'by keyword' and the channel parameter, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as fussballde_news for browsing without a keyword. Adequate but leaves routing to inference.

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