Retrieve current headlines for any Sporting News section by providing a sport, league, or topic slug. Fetches clean JSON from public US feeds.
Get Sporting News section headlines. Returns fresh headlines from one public Sporting News US sport, league or topic feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Sporting News section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful context by noting the feed is 'public' and 'fresh' and limited to 'one' feed, implying a read-only, current snapshot. However, it does not mention return format, pagination, rate limits, or authentication requirements, which are meaningful gaps for a tool without annotation safety hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with zero filler. It front-loads the main action and then adds a concise clarification of scope ('fresh,' 'public,' 'one feed'). Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read-only tool with no output schema, the description is largely sufficient: it states what is returned (headlines), the source (Sporting News US), and the parameter requirement (section). It lacks explicit return structure details, but this is a minor gap given the simplicity of a headlines endpoint.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the only parameter, 'section,' is fully described as a 'Sporting News section slug' with an explicit enum of valid values. The description adds no extra meaning to the parameter, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get Sporting News section headlines' and clarifies it returns 'fresh headlines from one public Sporting News US sport, league or topic feed.' This distinguishes it from generic headline tools by emphasizing 'section' and 'one ... feed,' though it does not explicitly name sibling tools like sportingnews_news or sportingnews_sections.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for fetching headlines from a specific section or feed, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. There is no mention of when not to use it or which sibling to choose for broader or different coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.