Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_team

Retrieve public FotMob team details by numeric team ID, including available sections like overview, table, fixtures, squad, stats, transfers, and history.

Instructions

FotMob team details. Returns public team data and the sections currently available for that team, such as overview, table, fixtures, squad, stats, transfers, and history. Team ids can be found with /fotmob/search. The upstream section set varies by team. For older fixtures, pass fixtures.previousFixturesUrl to /fotmob/team-fixtures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric FotMob team id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 discloses useful traits beyond the schema: output is public team data, the available section set varies per team, and older fixtures are not covered here. It doesn't mention rate limits or auth, but it covers the key behavioral caveats well.

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?

Front-loaded with the tool's purpose, then progressively adds retrieval hints and a caveat. Four sentences with no filler, though the section enumeration is slightly list-heavy.

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 single-parameter tool with no output schema, the description explains what data comes back (sections), notes variability, and points to the fixture alternative. Sufficient for correct invocation, missing only minor details like response shape stability.

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 there is only one required parameter (id), whose type is already documented as 'Numeric FotMob team id'. The description only reinforces that ids come from /fotmob/search, so the baseline of 3 applies.

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 (returns/gets) and resource (FotMob team details) and enumerates the content sections returned. It is clearly distinguishable from siblings like fotmob_team_fixtures or fotmob_search, which it cross-references.

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 concrete routing guidance: find ids via /fotmob/search and use /fotmob/team-fixtures (with fixtures.previousFixturesUrl) for older fixtures. It covers when to use this tool vs. those alternatives, though it doesn't state exclusions.

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