Skip to main content
Glama

yahoo_sports_topic_news

Read-only

Fetch public article cards for a Yahoo Sports topic slug or full topic_url, including Yahoo's embedded tags. Use yahoo_sports_home for the main page or yahoo_sports_navigation to discover section links.

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_topic_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional root topic slug, e.g. how-to-watch. Supply this or topic_url.
topic_urlNoOptional canonical Yahoo Sports topic page URL, including sport-scoped paths such as /golf/topic/lpga-tour/. Supply this or topic.

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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that the articles are public and include embedded tags, but does not cover pagination or rate limits; this is acceptable given the annotations and output schema.

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 tightly written sentences, with the core action and resource front-loaded and the alternative-tool guidance following immediately. There is no wasted wording.

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 simple read-only fetch tool with two optional parameters and an output schema, the description covers purpose, alternatives, and content type. It does not clarify what happens if both optional parameters are omitted, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are fully documented in the schema with examples. The description only restates that a topic slug or full topic_url is needed, adding no new semantics beyond the 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?

The description contains a specific verb ('Fetch'), a clear resource ('public article cards for a Yahoo Sports topic slug or full topic_url'), and notes the inclusion of embedded tags. It also distinguishes this tool from sibling tools yahoo_sports_home and yahoo_sports_navigation.

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

Usage Guidelines5/5

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

It explicitly directs agents to yahoo_sports_home for the main page and yahoo_sports_navigation for discovering section links. This provides clear alternatives and conditions, routing the agent appropriately.

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.