Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

national_author

Fetch public author profile data from The National, including name, image, and latest article cards, using a slug or topic page URL.

Instructions

Get a The National author profile. Returns one public author topic page, its name, optional author image and the latest article cards listed on that page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical thenationalnews.com/topics/Author/<slug> URL; alternative to slug
slugNoThe National author slug, e.g. cody-combs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return shape (topic page, name, optional image, latest article cards), which is genuinely useful given there is no output schema, but it omits the practical constraint that at least one of the two optional parameters must be supplied.

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 tightly written sentences, no waste, with the action stated first and the return payload second.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description compensates for the absent output schema by summarizing the return contents, but it fails to address the key operational requirement that a URL or slug must be provided despite both being marked optional. For a lookup tool with zero required params, that omission leaves a real gap.

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%, so both parameters are already documented with examples ('cody-combs', canonical URL format). The description adds no additional meaning beyond the schema baseline.

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 The National author profile') and enumerates what is returned, so an agent can distinguish this from national_article, national_headlines, and national_news. It does not explicitly name those siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the other National endpoints, nor any note that one of url or slug is needed to make a useful call. The agent must infer usage entirely from the schema.

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