Skip to main content
Glama

yahoo_sports_more_news

Read-only

Fetch one page of Yahoo Sports' public More News feed. Story records remain source-shaped and pagination values come from the live page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yahoo_sports_more_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page number from Yahoo's More News pagination. Defaults to 1.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld, but the description adds real signal: story records are 'source-shaped' (raw upstream payloads, not normalized) and pagination values are read from the live page, so an agent knows page counts cannot be assumed. It stops short of saying what an out-of-range page returns or whether the feed is rate-limited.

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?

Two short sentences with zero filler, and the resource identification is front-loaded ahead of the behavioral caveat.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers the two things an agent must know: this is a paged scrape and records are unnormalized. It is thin on end-of-feed and error behavior, which keeps it from a 5.

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% and the schema already documents the single 'page' argument as 1-based with a default of 1. The description adds value above that baseline by noting pagination values originate from the live page, hinting they may not be contiguous or predictable.

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 names a specific verb and resource ('Fetch one page of Yahoo Sports' public More News feed'), so an agent knows exactly what is returned. It falls short of a 5 because it never distinguishes the 'More News' feed from closely named siblings such as yahoo_sports_news, yahoo_sports_topic_news, or yahoo_sports_section_stream.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states no conditions for when to use this feed versus the many other Yahoo Sports news tools, and offers no exclusions or prerequisites. Only the phrase 'one page' implies anything about usage, which an agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.