Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

medicalnewstoday_article

Fetch public Medical News Today article metadata and body paragraphs from a canonical URL, rejecting robots-disallowed /articles/mnt-* paths. No login or paywall bypass.

Instructions

Get a Medical News Today article. Returns public article metadata and body paragraphs. No login or paywall is bypassed. URLs under the robots-disallowed /articles/mnt-* path are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Medical News Today article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (metadata + body paragraphs), the legal/ethical boundary ('no login or paywall is bypassed'), and a rejection rule for /articles/mnt-* paths. It omits error behavior and any rate limits, so it falls short of a 5.

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, all front-loaded and load-bearing: purpose, return content, and constraints. Nothing is redundant or padded.

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 no output schema and no annotations, the description adequately covers what the tool returns, its safety posture, and its input constraints. Error/failure behavior is the only notable gap for an agent to invoke it correctly.

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% for the single 'url' parameter, so the baseline is 3. The description adds marginal constraint value by noting that certain /articles/mnt-* URLs are rejected, but gives no format guidance beyond what the schema's 'Canonical Medical News Today article URL' already provides.

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?

States a specific verb and resource ('Get a Medical News Today article') and clarifies the payload ('public article metadata and body paragraphs'). It does not explicitly differentiate itself from siblings like medicalnewstoday_headlines or medicalnewstoday_news, though the 'article' naming makes the intent reasonably clear.

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 via the URL-based fetch model, but there is no explicit statement of when to use this versus medicalnewstoday_headlines, medicalnewstoday_news, or medicalnewstoday_sections. The robots-path rejection note constrains which URLs are valid but does not route the agent between sibling tools.

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