Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

techradar_headlines

Fetch TechRadar section headlines by section slug and return each story's title, URL, summary, publication time, author, and image.

Instructions

Get TechRadar section headlines. Returns the latest TechRadar stories for one section hub. section is required and takes one of 25 slugs such as computing, phones, audio, gaming, deals, reviews, news or vpn. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesTechRadar section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 usefully discloses the return shape (title, URL, summary, publication time, author, image) and that results are 'latest' stories, but says nothing about pagination, result counts, or rate limits.

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?

Three tight sentences with the core purpose front-loaded, followed by the required parameter and return fields. No filler, though the slug examples partially overlap the schema enum.

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 simple single-required-enum read tool with no output schema, the description covers purpose, the required parameter, and the returned item fields. Absent pagination/limits detail is a minor gap for a straightforward headlines fetcher.

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% and the enum already enumerates all slugs, so the schema does the heavy lifting. The description adds the count (25 slugs) and a few example values, but those examples largely duplicate the enum, so it adds only marginal value.

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 ('Get') and resource ('TechRadar section headlines') and clarifies scope as 'the latest TechRadar stories for one section hub'. It is clear what the tool does, but it does not name or differentiate itself from siblings like techradar_news or techradar_sections.

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?

It conveys that `section` is required and that the call targets one section hub, which implies usage. However, it gives no explicit when-to-use vs alternatives (e.g. versus techradar_news or techradar_sections), leaving the agent to infer.

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