Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

medicalnewstoday_author

Fetch a Medical News Today author profile by slug or URL to retrieve the author’s name, bio, and recent articles with summaries, dates, and images.

Instructions

Get a Medical News Today author profile. Returns a Medical News Today author profile by slug including its numeric id (for example peter-brown-1595) or by the profile url; provide one of the two. The response has the author's name, a bio when one is listed, and recent articles with title and URL, plus summary, date and image where present.

Input Schema

NameRequiredDescriptionDefault
urlNoPublic author profile URL
slugNoAuthor slug including numeric id, e.g. peter-brown-1595

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 and no output schema, the description carries the full burden and does disclose the read shape: name, conditional bio, recent articles with title/URL, and summary/date/image 'where present'. It doesn't discuss auth, rate limits, or how many recent articles are returned, but for a read-only profile lookup this is solid disclosure.

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-loaded with purpose, then identifier options, then return fields — a sensible order. It's three clauses in essentially two sentences with no filler, though the slug example is somewhat redundant with the 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?

Two optional identifier params, no annotations, and no output schema, so the description must explain both identifiers and the return payload — and it does. Nothing critical is missing for calling the tool; only peripheral details like result count are unstated.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond the schema by stating the two optional params are a one-of choice ('provide one of the two'), which the bare schema (both optional, no required) does not convey. The slug example duplicates the schema text but confirms the id-bearing format.

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 author profile') and immediately scopes it as author-profile retrieval, which separates it from medicalnewstoday_news/headlines/article/sections siblings. It never names a sibling or contrast condition, so differentiation relies on the agent inferring it from the resource noun.

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?

The description tells the agent it must supply an identifier and that either slug or url will do, which is genuinely actionable. It gives no when-to-use vs when-not guidance and never references the related Medical News Today tools, so usage is only implied by the resource name.

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