Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomshardware_headlines

Retrieve current headlines from one Tom's Hardware section by slug; returns each article's title, URL, author, publication time, lead image, and summary when provided.

Instructions

Get Tom's Hardware section headlines. Lists the current headlines for one Tom's Hardware section. section is required and takes a slug such as gpus, cpus, laptops, deals, reviews or news; use tomshardware-sections for the full set. Each item has its title, URL, author, publication time and lead image, plus a summary when the section's listing provides one.

Input Schema

NameRequiredDescriptionDefault
sectionYesTom's Hardware section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does reasonable work: it discloses that items contain title, URL, author, publication time and lead image, plus a summary only when the listing provides one. That output-shape and conditional-summary detail is genuinely additive, though auth/rate-limit behavior is unstated.

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 tight sentences, each earning its place: what it does, what the parameter requires plus the alternative, and what each item returns. Front-loaded with the core purpose.

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 no-annotation, single-enum-param tool with no output schema, the description covers purpose, parameter format, output fields and the sibling alternative. It is close to complete, though it omits count/pagination behavior that an agent might want.

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 20 slugs, so the schema does the heavy lifting. The description's example slugs (gpus, cpus, laptops, etc.) and the 'slug' format hint add marginal clarification but little beyond the enum. Baseline 3 is appropriate.

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 Tom's Hardware section headlines') with the scoping constraint ('one section') front and center. It names the sibling tomshardware-sections for the full set, so an agent can distinguish the two without opening a schema.

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

Usage Guidelines4/5

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

Explains that `section` is required and routes the agent to tomshardware-sections when the full set is wanted. Clear context for when to reach for it, though no explicit exclusions or prerequisites are given.

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