Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomshardware_article

Fetch a Tom's Hardware article by canonical URL and return structured JSON with title, authors, timestamps, images, paragraphs, and paywall status.

Instructions

Get Tom's Hardware article content. Returns one Tom's Hardware article by its canonical url, either the current tomshardware.com/<section>/<subsection>/<slug> form or the legacy /reviews/<slug>,<id>.html form. The response has the title, description, authors, section, published and updated times, lead image, the body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Tom's Hardware article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 response payload field-by-field (title, description, authors, section, times, lead image, paragraphs, paywalled flag) plus the legacy/new URL formats it accepts. It omits failure behavior (invalid URL, missing article) and any rate-limit or auth notes, but the return-shape disclosure is genuinely informative.

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: purpose first, then the URL forms, then the response contents. No filler, and the most decision-relevant information (what it does, what input it takes) is front-loaded.

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, no-annotation, no-output-schema tool, the description supplies enough to call it correctly and to know what comes back. The one meaningful gap is how the agent should obtain a valid URL, which is left implicit.

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% and the single url param is documented, so the baseline is 3. The description adds real meaning beyond the schema's terse 'Canonical Tom's Hardware article URL' by enumerating both accepted canonical forms, including the legacy /reviews/<slug>,<id>.html pattern.

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 article content') and specifies it returns one article by URL, which cleanly separates it from list-oriented siblings like tomshardware_headlines, tomshardware_news and tomshardware_sections. The two accepted URL forms further pin down exactly what input it consumes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, and no hint about where the required URL comes from (e.g., tomshardware_headlines or tomshardware_sections). The agent must infer that it is the article-detail step in the workflow.

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