Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomshardware_news

Fetch Tom's Hardware top stories as structured JSON, including titles, URLs, summaries, authors, publication times, and lead images. Use the URLs to read full articles.

Instructions

Get Tom's Hardware top stories. Returns the latest Tom's Hardware top stories with no parameters. Each item has its title, URL, summary, author, publication time and lead image. Use the item URLs with tomshardware-article to read the body.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the returned item shape (title, URL, summary, author, publication time, lead image), which is real value since there is no output schema. It omits pagination, item count, and refresh/freshness behavior, which are the main remaining unknowns for a listing tool.

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 short sentences, front-loaded with the action and resource. 'Returns the latest Tom's Hardware top stories' partly repeats the opening clause, a minor redundancy, but nothing is wasted overall.

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-parameter, no-output-schema listing tool, describing the returned fields is the key missing piece and it is provided. The only gap is absence of pagination or result-count information, which is minor given the tool's simplicity.

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?

Zero parameters, so the baseline is 4. The description correctly notes 'with no parameters', which is redundant against the empty schema but confirms no input is required, so nothing is misrepresented.

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 and resource ('Get Tom's Hardware top stories') and routes the agent to `tomshardware-article` for full bodies, which separates it from the article tool. It does not distinguish itself from the very similar `tomshardware_headlines` sibling, which an agent could easily confuse with 'top stories'.

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 gives one concrete piece of routing guidance ('Use the item URLs with `tomshardware-article` to read the body'), which is genuinely useful. However, it offers no when-to-use vs. the near-identical `tomshardware_headlines`/`tomshardware_sections` tools, so the primary selection decision is left implicit.

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