Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_news

Retrieve article previews from Flashscore News by category and page. Use category keys and pagination to browse headlines without full article text.

Instructions

Flashscore News listings by section. Returns article previews from a public Flashscore News section. Use flashscore-news-categories to discover valid category keys. Page numbers follow the site's Show more pagination; article body text is not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, 1 to 100; defaults to 1
categoryNoNews section key; defaults to all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the feed is public, returns previews rather than full text, and that pagination follows the site's Show more pattern. It does not mention rate limits or error behavior, but that is acceptable for a simple read endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with no filler. The opening sentence is mildly redundant with the tool name, but the rest is tight, front-loaded, and every additional sentence adds useful 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 two-parameter public listing tool with no output schema, the description covers purpose, category handling, pagination, and the key limitation (no body text). It does not detail return fields or ordering, but these are minor gaps for a previews-list endpoint.

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 the baseline is 3. The description adds meaning by explaining that page numbers follow the site's Show more pagination and by pointing to flashscore-news-categories for discovering valid category keys, which enriches both parameters 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 clearly states 'Returns article previews from a public Flashscore News section' – a specific verb and resource. 'By section' and 'previews' distinguish it from flashscore_news_article (full article) and flashscore_news_categories (discovery).

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

Usage Guidelines5/5

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

It explicitly instructs 'Use flashscore-news-categories to discover valid category keys', naming the sibling for a prerequisite. 'Article body text is not included' provides a clear when-not condition for when the agent should look elsewhere.

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