Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

techradar_article

Fetch a TechRadar article by canonical URL to get its title, description, section, authors, publication and update times, lead image, body paragraphs, and paywall status.

Instructions

Get TechRadar article content. Returns a TechRadar article by canonical url on techradar.com: title, description, section, authors, publication and update times, lead image, the body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical TechRadar article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 it does disclose the return shape in detail (title, section, authors, times, lead image, paragraphs) plus a `paywalled` flag, which is genuinely useful behavioral context. It omits any note on auth, rate limits, or failure modes, keeping it 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and then the payload fields. The field list is dense but each item earns its place since there is no output schema to carry that information.

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?

For a single-parameter fetch tool with no output schema, the description enumerates the returned fields, which is exactly what is needed. It lacks only guidance on sourcing the URL and error behavior, so it is strong but not exhaustive.

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 100% for the single url parameter, so the baseline is met. The description adds value by specifying that the url must be 'canonical' and scoped to techradar.com, which is meaning beyond the schema's plain 'Canonical TechRadar 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 (TechRadar article content) and immediately clarifies it returns an article by canonical url. This clearly distinguishes it from the sibling techradar_headlines, techradar_news, and techradar_sections tools.

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 agent must supply a canonical URL, which signals this is a detail-fetch tool rather than a listing tool. There is no explicit when-to-use or when-not, and no mention of how to obtain a valid URL from siblings like techradar_headlines.

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