Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_news_article

Fetch the full article body for a FotMob-authored top-news story using the complete id-and-slug from the /topnews/ URL. External publisher previews are not fetched.

Instructions

FotMob full top-news article. Returns the full article body for a FotMob-authored top-news story. Pass the complete id-and-slug value from the public /topnews/ URL. News previews from external publishers remain external and are not fetched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesComplete FotMob top-news article id and slug from the public article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses return content (full article body) and a scope constraint (only FotMob-authored stories, external ones are skipped), but says nothing about auth needs, rate limits, error behavior, or the exact response shape. Adequate but incomplete for a no-annotation tool.

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 tight sentences, front-loaded with what is returned, then the input format, then the scope exclusion. No filler or redundancy.

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-param, output-schema-less read tool, the description covers what is returned and how to construct the id. The main residual gap is behavioral detail (failure modes, response format) that no structured field supplies given the absence of annotations and output schema.

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 baseline is 3, but the description adds real value by emphasizing the parameter is a composite 'id-and-slug' value and naming the source URL path (/topnews/<id>), which warns the agent not to pass a bare numeric id.

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 ('Returns the full article body for a FotMob-authored top-news story'), which clearly distinguishes it from list-style siblings like fotmob_news or fotmob_latest_news. It stops short of explicitly naming an alternative, but the 'full article body' framing makes the retrieval-vs-list distinction clear.

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?

Tells the agent exactly how to obtain the input ('Pass the complete id-and-slug value from the public /topnews/<id> URL') and adds a scope exclusion ('external publisher previews remain external and are not fetched'). That exclusion functions as a when-not signal, though it never points to a sibling for the excluded case.

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