Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescore_news_feed

Fetch public LiveScore RSS news items across sports; optionally include full article content when available for feed monitoring or news aggregation.

Instructions

LiveScore global RSS news feed. Returns latest public news items from LiveScore's global RSS feed. The source feed may include multiple sports and has no verified category filter. Set include_content=true to include each RSS item's full content:encoded body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_contentNoInclude full RSS article content when available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses a key limitation (no verified category filter) and notes the feed may include multiple sports, which is useful behavioral context. However, it does not mention response format, pagination, or any other traits. Since no annotations are provided, the description carries the full burden and could be more transparent about the operation's behavior.

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, each adding new information: what it is, what it returns, and parameter guidance. No redundancy, and the key points are front-loaded. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should explain the return structure. It only says 'news items' without specifying fields, format, or pagination. Given the tool's simplicity, it still lacks essential details that an agent would need to effectively use the response.

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?

The schema describes include_content as 'Include full RSS article content when available.' The description adds specificity by mentioning 'content:encoded body,' clarifying exactly what content is included. This adds meaning beyond the schema alone.

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?

The description clearly states the tool returns latest public news items from LiveScore's global RSS feed. It also identifies a distinguishing characteristic—the feed may include multiple sports and lacks a verified category filter—which helps differentiate it from other news feed tools in the sibling list.

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 description provides specific parameter guidance (when to set include_content=true) but does not explicitly state when to use this tool versus alternatives or when not to use it. The caveat about multiple sports implicitly suggests it is not ideal for queries seeking a single sport, but this is left to inference.

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