Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cna_article

Fetch CNA article content by URL, returning title, authors, section, image, timestamps, and body paragraphs as structured JSON.

Instructions

Get CNA article content. Returns a CNA (Channel NewsAsia) article by url, a canonical channelnewsasia.com address such as /singapore/<slug>-<id> or /commentary/<slug>-<id>: title, description, publication and update times, section, authors, image and the body paragraphs. No paywalled or gated content was found during validation.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical CNA article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 burden; it does usefully disclose that the tool returns full body paragraphs and that no paywalled/gated content was observed during validation. It stops short of stating anything about rate limits, auth, or error behavior for malformed/non-canonical URLs, which would matter for a no-annotation tool.

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 sentences, front-loaded with the verb and resource, then the return payload and the URL format constraint. No filler sentences and nothing repeated from structured fields.

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 compensates well by listing the returned fields and the URL format. It could go slightly further on failure modes or non-canonical URLs, but for a single-parameter read tool it is essentially complete.

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% for the single url parameter, so the baseline is 3; the description earns extra credit by giving concrete path shapes ('/singapore/<slug>-<id>', '/commentary/<slug>-<id>') that clarify what a valid canonical value looks like beyond the schema's terse 'Canonical CNA article URL'.

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 ('Get') and resource ('CNA article content') and pins the retrieval mode to a single article via 'url', which implicitly separates it from cna_headlines/cna_news/cna_sections sibling listing tools. It also enumerates exactly what is returned (title, description, times, section, authors, image, body paragraphs), leaving no ambiguity about the tool's output.

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 only implied: the required canonical URL parameter signals 'fetch one already-known article', but the description never states when to pick this over cna_news or cna_headlines, nor any prerequisites beyond valid URL form. The note that no paywalled content was found adds practical context but is not routing guidance.

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