Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomshardware_author

Retrieve a Tom's Hardware author's public profile, including biography, social links, and recent articles, using their author slug or URL.

Instructions

Get a Tom's Hardware author profile. Returns one Tom's Hardware author's public profile: name, biography, social links, and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical tomshardware.com/author/<slug> URL, optionally with a /page/<n> segment; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. christian-eberle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds a useful behavioral detail ('one page of their recent articles') and 'public profile' implies a read-only operation, but it does not explicitly confirm no side effects, error behavior, or auth/rate-limit requirements. Adequate for a simple read tool, but not rich.

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?

Two dense sentences with no filler. The core action is front-loaded, and the return fields are listed compactly in a single clause. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lists the key return fields and mentions pagination, which is helpful given there is no output schema. However, it leaves ambiguity about how to select an author when all parameters are optional and does not explain behavior when no argument is supplied. Adequate but has clear gaps.

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%, so the baseline is 3. The description adds no parameter-level guidance beyond the schema and does not clarify whether at least one of slug or url is required, despite all params being optional in the schema.

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 a Tom's Hardware author profile') and enumerates the returned fields: name, biography, social links, and recent articles. This clearly distinguishes it from sibling tools like tomshardware_article, tomshardware_headlines, and other author-profile 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?

Implies use when an agent needs an author's public profile, but does not explicitly state when to prefer this tool over alternatives or when not to use it. No sibling tools are named, and there is no exclusion guidance, so the agent must infer the use case from the name and description.

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