Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_tv_guide_channels

Discover TV channels showing matches in a selected country within the current seven-day public guide window. Provide a country code to return match channel listings.

Instructions

FotMob TV guide channels. Discovers channels attached to matches in the selected country's current seven-day public TV guide window. Use the country directory to discover the complete country code set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesMarket code from /fotmob/tv-guide-countries

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?

No annotations, so the description carries the burden. It implicitly signals a read-only discovery operation ('Discovers') and discloses two meaningful constraints — the seven-day window and 'public' scope. It does not mention return shape, pagination, or reliability, so gaps remain.

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?

Two tight sentences with the core scope front-loaded after a short identifier, and the country-directory hint appended. No filler, though the leading 'FotMob TV guide channels' fragment is slightly redundant with the name.

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 read-only, single-enum-param discovery tool with no output schema and no annotations, the description covers purpose, temporal scope, and parameter sourcing adequately. Missing only return-format and pagination detail, which is minor here.

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 the single param is fully documented in the schema ('Market code from /fotmob/tv-guide-countries'), so baseline 3. The description's mention of the country directory largely repeats what the schema already says, adding little beyond it.

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+resource ('Discovers channels attached to matches') and scope ('selected country's current seven-day public TV guide window'). This distinguishes it reasonably from the generic fotmob_tv_guide, though it never explicitly names that sibling as the alternative.

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?

Provides one useful routing hint — 'Use the country directory to discover the complete country code set' — which points at fotmob_tv_guide_countries. But it gives no when-to-use-this vs fotmob_tv_guide guidance and no 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