Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyrecord_article

Fetch a Daily Record article by canonical URL to get its title, description, dates, section, authors, lead image, body paragraphs, and paywall status.

Instructions

Get Daily Record article content. Returns one Daily Record article by its canonical article url. The response has the title, description, publish and update times, section, authors, lead image, body paragraphs and a paywalled flag. Subscriber-only or blocked articles return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Daily Record article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 enumerates the response contents (title, description, publish/update times, section, authors, lead image, paragraphs, paywalled flag) and discloses that subscriber-only or blocked articles return an upstream error — a genuinely useful failure-mode disclosure. Missing only auth/permission requirements and rate-limit behavior.

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 sentences, zero filler, front-loaded with the action and scoped progressively to the input, the return shape, and the failure case. Every sentence earns its place.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the paywall/blocked error path. For a one-parameter read tool this is close to complete; a note on how to source the URL or pagination/auth caveats would close the remaining 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 coverage is 100% with a single required `url` parameter already documented as 'Canonical Daily Record article URL'. The description's mention of the canonical URL adds virtually nothing 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.

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 Daily Record article content') and immediately narrows scope to fetching one article by its canonical URL. An agent can distinguish this from dailyrecord_headlines, dailyrecord_news, dailyrecord_sections, and dailyrecord_author without opening any schema.

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 the singular-article framing and the 'one Daily Record article by its canonical article url' phrasing, but it never states when to prefer this over dailyrecord_news or how to obtain the URL (e.g., from a headlines call). No explicit alternatives or exclusions.

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