Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

medicalnewstoday_headlines

Retrieve Medical News Today Health News headlines for the news section, returning dated story cards with titles, URLs, dates, authors, summaries, and images.

Instructions

Get Medical News Today section headlines. Returns the dated story cards from the Medical News Today Health News stream. section is required and currently accepts only news; medicalnewstoday-sections shows the accepted value. Each item has a title and URL, with a publication date such as 2026-09-26, author, summary and image when the card shows them.

Input Schema

NameRequiredDescriptionDefault
sectionYesMedical News Today newsroom section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does describe the returned story-card fields (title, URL, publication date, author, summary, image), which is genuinely useful. But it says nothing about pagination, auth needs, rate limits, or whether the listing is bounded, so the disclosure is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and then the required-parameter constraint, with no filler sentences. The enumeration of return fields is a little dense but each element carries information an agent would otherwise lack given there is no output schema.

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 one-parameter read tool with no output schema, the description covers purpose, the single parameter's constraint, and the item shape. Missing only pagination/limit behavior, which is minor for a headline stream.

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% and the enum already shows the single accepted value `news`. The description largely restates that constraint ("required and currently accepts only `news`"), adding only the routing hint to the sections sibling rather than real syntax or format detail. Baseline 3 is appropriate.

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 and resource ("Get Medical News Today section headlines") and defines scope as the Health News stream. It also names the related sibling 'medicalnewstoday-sections', letting an agent distinguish the headline fetch from the sections lookup.

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?

It clearly states that `section` is required and currently accepts only `news`, and points to `medicalnewstoday-sections` for discovering accepted values. However, it does not explicitly state when to use this tool versus alternatives like `medicalnewstoday_news` or `medicalnewstoday_article`.

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