Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_team_results

Flashscore team results. Returns one page of a team's finished and in-progress matches, newest first, as structured events with start time, stage, both sides, score and competition. Event ids work with the flashscore match endpoints.

Instructions

Flashscore team results. Returns one page of a team's finished and in-progress matches, newest first, as structured events with start time, stage, both sides, score and competition. Event ids work with the flashscore match endpoints. Request successive pages until event_count is 0; a page past the end returns an empty list.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore team id
pageNo1-based page from 1 to 300; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose meaningful traits: newest-first ordering, the exact fields each event contains, the pagination termination signal (event_count reaching 0), and the empty-list behavior past the end. It stops short of auth/permission or rate-limit behavior, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with the purpose and scope before the return-shape detail and pagination instructions. Every sentence contributes distinct information with no redundancy.

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?

There is no output schema, so the description must describe returns, and it does so adequately (start time, stage, both sides, score, competition) while also explaining pagination and the event-id interop with match endpoints. It is complete enough to call the tool correctly, with only minor gaps like no explicit tie to sibling 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 description coverage is 100% (id and page are fully documented in the schema), so the baseline is 3. The description adds pagination context but no meaning about the parameters themselves (e.g., id format or page bounds) that exceeds 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?

The description gives a specific resource ('a team's finished and in-progress matches') and the shape of the return, so the scope is unambiguous. The 'finished and in-progress' phrasing implicitly separates it from the upcoming-oriented siblings like flashscore_team_fixtures, but no sibling is named explicitly, which keeps 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?

It gives concrete pagination guidance ('request successive pages until event_count is 0; a page past the end returns an empty list'), which is useful operational instruction. However, it never states when to choose this tool over flashscore_team_fixtures, flashscore_team, or the player-results siblings, so the when-to-use guidance is only implied.

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