Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_navigation

Returns Yahoo Sports navigation labels and URLs for the home page or a specified public section, enabling discovery of sport-scoped topics and filters.

Instructions

Yahoo Sports section navigation. Returns the exact navcat label and URL links Yahoo renders on the home page or one public sports section page. Use section_url from yahoo-sports-home or this response to discover sport-scoped topics and filters.

Input Schema

NameRequiredDescriptionDefault
section_urlNoFull Yahoo Sports page URL; leave blank for home navigation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool returns Yahoo-rendered navcat labels and URL links and implies read-only browsing, but does not discuss rate limits, permissions, or response-shape constraints beyond labels and links.

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 short sentences, front-loaded with the tool's identity and return content, followed by the actionable usage note. There is no filler.

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 one-parameter navigation tool with no output schema and no annotations, the description covers what is returned and how to proceed recursively. It could be slightly richer about the response structure or when not to call it, but it is sufficient for correct invocation.

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%, so the parameter is already documented. The description still adds useful semantics by explaining where section_url should come from and how recursive navigation can be used to discover sport-scoped topics and filters.

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 states a specific resource and output: Yahoo Sports section navigation returning navcat labels and URL links from the home page or a public section page. It is clearer than a generic navigation tool, though it does not explicitly contrast itself with nearby siblings like yahoo_sports_home or yahoo_sports_leagues.

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 gives actionable usage guidance: use section_url from yahoo-sports-home or from this response to discover sport-scoped topics and filters, and the schema clarifies that blank returns home navigation. It stops short of naming exclusion cases or alternative tools to use instead.

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