Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_tv_guide

Fetch a country's seven-day football TV broadcast schedule with local kickoff times, using a market code and optional IANA timezone.

Instructions

FotMob football TV guide. Returns the public seven-day football broadcast schedule for a country, with local schedule times. Discover all accepted country codes from /fotmob/tv-guide-countries. Timezone defaults to UTC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesMarket code from /fotmob/tv-guide-countries
timezoneNoIANA timezone for local times

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.9/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 does disclose meaningful behavior: it is a read operation ('Returns'), the data is public, the window is a fixed seven days, and timezone defaults to UTC. It omits pagination/result-size behavior, which is the main remaining gap.

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, purpose front-loaded, zero filler. Each sentence adds distinct information: what it returns, where to get country codes, and the timezone default.

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 simple country-scoped lookup with a rich enum schema and no output schema, the description covers purpose, temporal scope, timezone behavior, and country-code discovery. The only shortfall is that return shape/pagination is not described, though the return content is summarized.

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 both parameters are already documented, establishing a baseline of 3. The description goes beyond the schema by stating the timezone default (UTC) and pointing to the country-code discovery tool, adding real semantic value.

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 verb and resource: 'Returns the public seven-day football broadcast schedule for a country.' The scope (seven-day window, per-country, broadcast schedule) is concrete. It does not explicitly differentiate itself from siblings like fotmob_tv_guide_channels or fotmob_tv_guide_countries, but the resource is unambiguous.

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?

Usage is implied rather than stated: it tells the agent to 'Discover all accepted country codes from /fotmob/tv-guide-countries', which is a useful prerequisite pointer to a sibling. However, there is no explicit when-to-use/when-not guidance or differentiation from the channels variant.

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