Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_entity_news

Flashscore news for a team, player, tournament or sport. Returns the article ids of Flashscore's own news layout for one entity: the featured article plus the 25 most recent ones, grouped in the sections Flashscore shows.

Instructions

Flashscore news for a team, player, tournament or sport. Returns the article ids of Flashscore's own news layout for one entity: the featured article plus the 25 most recent ones, grouped in the sections Flashscore shows. The layout has no pagination. Resolve the ids with flashscore-news-article (metadata) or flashscore-news-article-body (full text). Teams and players share one layout type. A tournament is a tournament template id (the competition id in event lists); a sport is one of the SPORT entity ids listed by flashscore-news-categories. An id with no news layout returns not found.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character entity id: team or player id, tournament template id, or a SPORT entity id from flashscore-news-categories
typeYesEntity type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

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 and does so fairly well: it discloses the return shape (article ids, featured + 25 recent, sectioned), that the layout has no pagination, and the error behavior ('an id with no news layout returns not found'). It omits auth/rate-limit context but covers the operationally important traits.

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?

Front-loads the purpose before the return details, id resolution, and error case. It is dense and runs long for a two-parameter tool, but nearly every sentence carries distinct 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?

With no output schema and no annotations, the description is complete enough: it explains return contents, pagination absence, id sourcing per type, and not-found behavior. The main gap is routing guidance against the sibling news tools.

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 coverage is 100%, so the baseline is 3. The description restates and slightly enriches the id semantics ('a tournament template id (the competition id in event lists)', sport ids from flashscore-news-categories), but adds little beyond what the schema's own parameter descriptions already say.

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 ('Flashscore news for a team, player, tournament or sport') and describes the payload (featured + 25 recent article ids, grouped in sections). However it never names or distinguishes itself from overlapping siblings like flashscore_team_news, flashscore_player_news, or flashscore_news, so an agent must infer the boundary.

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 context for use: which entity types are valid, what the id must be for each type, and how to resolve the returned ids via flashscore-news-article or flashscore-news-article-body. It stops short of explicit when-not-to-use against the entity-specific sibling tools.

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