Crawlora MCP

yahoo_health_category

Read-only

Returns a Yahoo Health section's editorial story feed: title, destination URL, category, and thumbnail image for each story, with page-based pagination.

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": {
      "category": "<category>"
    },
    "name": "yahoo_health_category"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number, defaults to 1
`category`	Yes	Yahoo Health section. Documented values: conditions, general, healthcare, treatments, wellness, your-body.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / category / description

Added value: +"Yahoo Health section. Documented values: conditions, general, healthcare, treatments, wellness, your-body."

addedInput schema / properties / page / description

Added value: +"1-based page number, defaults to 1"

First observedOct 5, 2026

TDQS

A3.6/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 results are paginated by page number, which is useful, but says nothing about rate limits, ordering, or how the feed updates.

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?

A single front-loaded sentence that packs the resource, return fields, and pagination behavior with 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?

With an output schema present and annotations covering the safety profile, the description is largely complete; the category enum lives in the schema. The only gap is the absence of any routing hint versus its yahoo_health_* siblings.

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%: both 'page' and 'category' are fully documented in the schema, including the six category values. The description only restates page-based pagination and the notion of a section, adding little beyond the schema, so the baseline 3 applies.

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?

Names a specific verb+resource ('Returns a Yahoo Health section's editorial story feed') and enumerates the returned fields, so the agent knows exactly what this tool produces. It does not explicitly contrast itself with yahoo_health_home or yahoo_health_article, but the 'section feed' scoping makes its role distinguishable.

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

Usage Guidelines3/5

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

Usage is implied by 'section's editorial story feed' and the required category parameter, but there is no explicit guidance on when to choose this over yahoo_health_home or yahoo_health_article. No exclusions or prerequisites are stated.

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

All Crawlora MCP tools Inspect

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

Need Help?