Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescore_news

Fetch LiveScore news article cards by required category or lowercase route path, such as football/premier-league. Use all for the home feed.

Instructions

LiveScore news by category or topic. Returns the article cards for one LiveScore news route. category is required: all for the home feed, or a lowercase route path of up to six segments, such as football/premier-league, found via livescore-news-categories. The response carries source_url and the page data. Some articles link to third-party publishers, article bodies are not returned, and unknown paths return not found or an upstream error.

Input Schema

NameRequiredDescriptionDefault
categoryYesall or a lowercase path from /livescore/news-categories; up to six segments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries real behavioral weight: it discloses that responses carry `source_url` and page `data`, that some links point to third-party publishers, that bodies are omitted, and that unknown paths yield not-found or upstream errors. That error-mode and scope disclosure is exactly the kind of context the agent cannot get from the schema.

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 purpose followed by the parameter contract and then caveats. Dense and mostly waste-free, though the dangling clause about third-party publishers and error paths packs several distinct points into one sentence.

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-parameter tool with no output schema, the description covers purpose, parameter sourcing, response shape, content limits, and failure behavior. The main omission is explicit routing against sibling news tools, which a slightly longer description could have closed.

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 already 100%, so the baseline would be 3, but the description adds genuine meaning: `all` maps to the home feed, other values are lowercase route paths up to six segments, and valid values come from `livescore-news-categories`. That is more than the schema field text conveys.

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?

The description gives a specific verb and resource ("LiveScore news by category or topic", "returns the article cards for one LiveScore news route") and names the sibling `livescore-news-categories` as the source of valid categories. However, it never distinguishes itself from close siblings such as `livescore_news_feed` or `livescore_news_article`, so an agent must still infer which one to pick.

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?

It states the category requirement concretely: `all` for the home feed or a lowercase route path obtained via `livescore-news-categories`, which is actionable selection guidance. It also hints at when not to expect article text ("article bodies are not returned") without naming the alternative tool that would return them.

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