Crawlora MCP

flashscore_entity_news

Read-only

List the article ids in Flashscore's news layout for one team, player, tournament or sport: the featured article plus the 25 most recent, grouped by section. Pass type (team, player, tournament, sport) and an entity id; sport ids come from flashscore_news_categories. Resolve the ids with flashscore_news_article_body for full text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "flashscore_entity_news"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required eight-character entity id: a team or player id, a tournament template id (the competition id in team results and score feeds), or for type sport one of the entity ids listed by flashscore-news-categories (entity_type SPORT).
`type`	Yes	Required entity type: team, player, tournament or sport. team and player share the participant news layout.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context: the exact result shape (featured article plus the 25 most recent) and grouping by section, which the annotations cannot convey.

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 sentences, front-loaded with the returned resource, then the call syntax and follow-up tool. No filler; every clause earns its place.

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?

With an output schema present and readOnly/openWorld annotations supplied, the description covers the remaining need: what is returned, how to call it, and how to resolve ids. Nothing an agent needs to invoke it correctly is missing.

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% and it already enumerates the type values and explains the id semantics, including the SPORT entity-id sourcing. The description merely restates the type values and repeats the news-categories cross-reference, adding no new parameter detail.

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?

States a specific verb (List) and resource (article ids in Flashscore's news layout) scoped to a single entity, with exact content (featured + 25 most recent, grouped by section). An agent can distinguish this id-listing tool from the full-text and generic news siblings.

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?

Gives clear routing: pass type+id, source sport ids from flashscore_news_categories, and resolve returned ids with flashscore_news_article_body. It does not explicitly address when to prefer this over flashscore_team_news or flashscore_player_news, hence not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?