Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_team_squad

Flashscore team squad. Returns a team's squad grouped by position (goalkeepers, defenders, and so on, plus the coach) with each person's jersey number, age, country (or club, for national teams), injury or absence note and season…

Instructions

Flashscore team squad. Returns a team's squad grouped by position (goalkeepers, defenders, and so on, plus the coach) with each person's jersey number, age, country (or club, for national teams), injury or absence note and season statistics. The default scope totals all competitions; the scopes list in every response names the per-competition scopes accepted by the scope parameter. Sports without a squad page return not found.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore team id
slugNoOptional team slug; must match the id when supplied
scopeNoSquad statistics scope key from the scopes list of a previous response (for example overall-all or league-SY30SsKF); defaults to overall-all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.5/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 behavioral burden and does so well: it discloses the return grouping/fields, the scope default and per-competition behavior, and the not-found edge case. It omits only minor traits such as read-only framing (implied) or any rate/permission notes, which are not critical for a public sports-data read.

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 what the tool returns, then scope behavior, then the edge case. Every sentence adds usable information with no filler or redundancy.

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?

There is no output schema, so the description must describe return values — and it does (grouped squad, per-person fields). All three parameters are documented, and the scope mechanics plus the not-found case round out what an agent needs to call it correctly.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that the default scope totals all competitions and that the scopes list in each response names the valid per-competition scope keys. This clarifies the semantics of the `scope` parameter rather than merely restating it.

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 and resource — returns a team's squad — and details the exact output structure (position groupings, coach, jersey number, age, country/club, injury note, season stats). An agent can distinguish it from flashscore_team, flashscore_team_fixtures, or flashscore_player without opening any 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 clear context: default scope totals all competitions, and the accepted per-competition scopes are discoverable from the scopes list in a response. It also names a when-not case (sports without a squad page return not found). It does not, however, explicitly contrast against sibling tools like flashscore_team, so it stops short of full alternative routing.

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