Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_trending_news

Fetch the five-story FotMob football Trending news shelf to see curated previews from the public News page.

Instructions

FotMob trending football news. Returns the five-story Trending shelf shown on FotMob's public News page. Items are curated previews and may overlap the global latest-news feed; the upstream list is dynamic. No locale or country parameter is exposed because the complete accepted value space is not pinned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

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 does reasonably well: it discloses the fixed five-item cardinality, that items are curated previews, that overlap with the latest-news feed is possible, and that the upstream list is dynamic. Auth, rate limits, and response shape are unspecified, but for a public read endpoint the behavioral disclosure is above average.

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 sentences, front-loaded with what is returned, followed by curation/volatility caveats and the no-parameter rationale. All sentences are informative, though the final sentence reads slightly as defensive justification rather than actionable guidance.

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 zero-parameter, no-output-schema endpoint, the description covers what the tool returns, how many items, their provenance, and their volatility. Nothing essential is missing for correct invocation, though it stops short of describing item fields.

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?

Zero parameters, so baseline is 4. The description additionally justifies the absence of a locale/country parameter, proactively telling the agent not to hunt for a filtering option that does not exist.

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 the five-story Trending shelf shown on FotMob's public News page'), including cardinality and source location. It also implicitly contrasts with the global latest-news feed, which maps to the sibling fotmob_latest_news, so an agent can distinguish it from adjacent tools.

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?

The note that items 'may overlap the global latest-news feed' hints that this is a curated subset rather than the full feed, but it never explicitly says when to prefer this tool over fotmob_latest_news. Usage is implied rather than stated.

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