Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_match_standings

Fetch match-linked league standings by match ID, with views for overall, home/away, form, over/under, half-time/full-time, live table, or top scorers.

Instructions

Flashscore match league standings. Returns the match-linked table feed. Select overall, home/away, form, over/under, half-time/full-time, live table, or top scorers; the raw provider format is preserved. Defaults to overall.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEight-character Flashscore match id
viewNoStandings/table view; defaults to overall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 that the raw provider format is preserved, that the default view is overall, and that the result is a table feed, which are meaningful behavioral details beyond the schema. It does not cover every edge case, but it is sufficient for a read-only data fetch.

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?

The description is compact and front-loads the purpose, then enumerates view options and default behavior. The opening phrase repeats the tool name and adds little, so it is not perfectly economical, but there is no waste beyond that.

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 read tool with no output schema, the description covers what it returns (a table feed), that the format is raw, and how to select views, while the schema covers id and view values. It could be more explicit about the feed contents or error/empty behavior, but an agent has enough to invoke it correctly.

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% and both params are already described, so the baseline is 3. The description adds only grouping of the view enum values and restates the default, with no new semantic detail about the id parameter.

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 resource ('match-linked table feed') and a return action, with a useful list of selectable views. It is clear enough to understand the tool's job, though it does not explicitly contrast with sibling standings tools like flashscore_tournament_standings.

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?

The description implies usage context through the required match id and phrases like 'match-linked', so an agent can infer it is for standings tied to a specific match. It does not give explicit when-to-use/when-not-to-use guidance or name alternatives, leaving selection among flashscore siblings to inference.

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