Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_player_news

Flashscore player news. Returns up to 100 recent headlines about a player, aggregated from news publishers, with publisher, publication time and image. Links point to Flashscore's redirect to the publisher.

Instructions

Flashscore player news. Returns up to 100 recent headlines about a player, aggregated from news publishers, with publisher, publication time and image. Links point to Flashscore's redirect to the publisher. A player without news returns an empty list. A team id returns not found, use flashscore-team-news for teams.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.4/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 well: it discloses the <=100 headline cap, publisher aggregation, returned fields (publisher, publication time, image), redirect-style links, the empty-list behavior, and the not-found failure mode for wrong id type. It omits auth/rate-limit details, but for a read-only news tool this is strong disclosure.

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 core return, then the field/link details, then two edge cases with the sibling pointer. Every sentence adds distinct information with no filler.

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?

No output schema exists, so the description must (and does) describe the return shape: headlines with publisher, publication time, image, and redirect links. Combined with the empty-list and not-found edge cases, it is essentially complete for a single-parameter tool; only pagination/truncation behavior at the 100 cap is unaddressed.

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% and the schema already documents the eight-character player id, so the baseline is 3. The description adds real meaning by clarifying the id must be a player id: passing a team id yields not found, which constrains valid values 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?

States a specific verb+resource: returns recent headlines about a player, with the count cap. It explicitly contrasts itself with the sibling flashscore-team-news for the team case, so an agent can distinguish it without opening either schema.

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 a clear when-not condition and names the alternative ('A team id returns not found, use flashscore-team-news for teams'), plus the empty-list case for players without news. It does not address how it relates to other news siblings (flashscore_news, flashscore_entity_news), so guidance is good but not exhaustive.

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