Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_news_suggest

Read-only

Fetch Yahoo News search-box autocomplete suggestions for a partial query. Use yahoo_search_suggest for general web-query suggestions, or yahoo_news_home and yahoo_news_category when you need story results rather than query completions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "yahoo_news_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesPartial search query to autocomplete
countNoNumber of suggestions to return, default 10, clamped to 1..20

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. Changed2 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"Number of suggestions to return, default 10, clamped to 1..20"
    • addedInput schema / properties / q / description
      Added value: +"Partial search query to autocomplete"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description clarifies that output is search-box completions rather than documents, which is useful context, but adds nothing about rate limits, coverage, or result shape beyond that.

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 sentences with zero waste; the core purpose is front-loaded and the routing guidance follows immediately. Every clause earns its place.

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?

With an output schema present, return values need no explanation, and the purpose plus routing guidance are sufficient for a simple autocomplete tool. Only minor behavioral detail (e.g. freshness or scope of suggestions) is absent.

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 coverage is 100%: q is documented as the partial query and count carries its default and 1..20 clamp. The description only restates the partial-query concept, adding no syntax or usage nuance 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?

States a specific verb (fetch) and resource (Yahoo News search-box autocomplete suggestions) and scopes it to a partial query. It explicitly distinguishes itself from yahoo_search_suggest and the news story tools, so an agent can route correctly without opening schemas.

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?

Names the alternative tools and the conditions selecting each: yahoo_search_suggest for general web queries, yahoo_news_home/yahoo_news_category for story results rather than completions. When-to-use and when-not-to-use are both explicit.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources