Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_team

Flashscore team profile. Returns a team's public profile: name, country, sport, logo, the stadium and capacity shown on its summary page, and the competitions of its recent and upcoming fixtures.

Instructions

Flashscore team profile. Returns a team's public profile: name, country, sport, logo, the stadium and capacity shown on its summary page, and the competitions of its recent and upcoming fixtures. Use a team id from flashscore-search, a Flashscore team URL, a match endpoint's team ids, or flashscore-team-squad and flashscore-player. A player id returns not found.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore team id

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 behavioral load and does well: it enumerates the returned fields and discloses the not-found failure mode for player ids. It also hints at the data source by noting the stadium/capacity is what's "shown on its summary page." It does not mention rate limits, auth, or pagination, but for a simple read-only lookup this is minor.

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?

Four short sentences, front-loaded with the purpose and return contents before the id-source guidance and the not-found caveat. Dense but every sentence carries distinct information; nothing is padded.

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 describe return values, and it does so field by field. No annotations exist, and it covers the primary error case; only auth/pagination/rate-limit context is absent, which is acceptable for a lookup tool.

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% (the single id param is documented), so a 3 would be the baseline. The description adds value beyond the schema by expanding accepted input formats beyond the schema's "Eight-character Flashscore team id" (it accepts a Flashscore team URL) and by clarifying which sibling tools yield valid ids.

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 public profile") and enumerates exactly what comes back: name, country, sport, logo, stadium/capacity, and recent/upcoming fixture competitions. This clearly distinguishes it from siblings like flashscore_team_fixtures, flashscore_team_squad, and flashscore_team_results, which cover subsets of that data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names four acceptable id sources (flashscore-search, a Flashscore team URL, a match endpoint's team ids, flashscore-team-squad and flashscore-player) so the agent knows how to obtain the required input. It also states an exclusion — "A player id returns not found" — which steers the agent away from the most likely wrong-id mistake.

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