Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportingnews_sections

Lists the 44 Sporting News US sport, league, and topic feeds accepted by the headlines tool, with each feed's slug, name, and URL.

Instructions

Get Sporting News sections. Lists the 44 Sporting News US sport, league and topic feeds that sportingnews-headlines accepts. Each entry has a slug, a display name and the feed url. Off-season leagues such as club-world-cup and softball are listed and may return older items. Team feeds and non-US editions are not covered.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 well: it discloses the exact entry shape (slug, name, url), warns that off-season leagues like `club-world-cup` and `softball` may return older items, and states coverage limits. It omits any auth, rate-limit or ordering caveats, so it is strong but not exhaustive.

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 the core purpose, then the feed count, then the entry shape, then the caveats. Every sentence contributes: the off-season warning and the coverage exclusions both prevent wrong calls.

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

Completeness5/5

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

For a zero-parameter list tool with no output schema, the description supplies the return structure, the exact cardinality, the valid-target relationship, and the edge cases. An agent has everything needed to call it and interpret the result.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It does add return-field meaning (slug/name/url) which is beyond the empty input schema.

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 ('Get Sporting News sections') and immediately defines the resource precisely: the 44 US sport, league and topic feeds. It explicitly ties itself to the sibling `sportingnews-headlines`, letting an agent distinguish this discovery tool from the article/author/news siblings without opening any schema.

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?

The phrase 'the 44 ... feeds that `sportingnews-headlines` accepts' clearly signals the dependency — this is the lookup you use to obtain valid slugs for the headlines tool — and it names exclusions (team feeds, non-US editions are not covered). It stops short of an explicit 'call this before headlines to resolve a slug' instruction, but the routing is easy to infer.

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