Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_lineup_builder_team

Retrieve a FotMob team's prefilled formation, starting lineup, and squad list by team id to build lineup data. Some teams may have no squad list.

Instructions

FotMob lineup builder team data. Returns the public lineup builder's prefilled formation, starting lineup, and squad for a team id. Discover open-ended team ids with /fotmob/search. Some teams legitimately have no squad list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYesNumeric FotMob team id discoverable through /fotmob/search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does add value: it discloses the returned payload shape and warns that 'some teams legitimately have no squad list,' an edge case an agent needs. However, it omits auth requirements, rate limits, or what an empty result response looks like beyond the squad caveat.

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?

Three short sentences, appropriately front-loaded with the payload description before the discovery hint and the empty-result caveat. The opening phrase 'FotMob lineup builder team data' is mildly redundant with the tool name but the rest earns its place.

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 one-parameter read tool with no output schema and no annotations, the description adequately covers what is returned and how to obtain the id, plus the notable empty-squad case. Only minor gaps around return format or failure behavior remain.

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%, so the schema already documents team_id as a numeric FotMob id discoverable via /fotmob/search. The description reinforces the same information but adds no new syntax, format, or constraint beyond the schema, so the baseline of 3 applies.

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 names a specific verb (returns) and enumerates the resource contents: the lineup builder's prefilled formation, starting lineup, and squad. It is clear what the tool delivers, though it does not explicitly distinguish itself from the sibling fotmob_lineup_builder_players, so it falls short of the 5 bar.

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 a concrete discovery path ('Discover open-ended team ids with /fotmob/search'), which is useful usage context, but it never states when to use this tool versus sibling endpoints like fotmob_team or fotmob_lineup_builder_players. Usage is implied rather than contrasted.

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