Crawlora MCP

techradar_author

Read-only

Fetch one TechRadar author's public profile: name, job title, biography, social links, and one page of their recent articles. Use techradar_article for one story's content. Use techradar_headlines and techradar_news for current outlet feeds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "techradar_author"
  }
}

Input Schema

Name	Required	Description
`url`	No	Canonical techradar.com/author/<slug> URL, optionally with a /page/<n> segment; alternative to slug
`page`	No	1-based page number; overrides any page number in url
`slug`	No	Author slug, e.g. tom-power

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / page / description

Added value: +"1-based page number; overrides any page number in url"

addedInput schema / properties / slug / description
```
Added value: +"Author slug, e.g. tom-power"
```

addedInput schema / properties / url / description

Added value: +"Canonical techradar.com/author/<slug> URL, optionally with a /page/<n> segment; alternative to slug"

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavioral context by stating it returns 'one page of their recent articles,' disclosing pagination scope. It stops short of noting rate limits or auth, but for a read-only fetch that is a minor gap.

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 with zero filler: purpose first, then two routing sentences. Every clause earns its place and the core action is front-loaded.

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

Completeness5/5

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

With an output schema present, the description needn't detail return values, yet it still summarizes the profile contents. Combined with full schema coverage and sibling routing, nothing an agent needs to call this correctly is missing.

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 schema already documents url, page, and slug fully (including the url/slug alternative and page override). The description adds no parameter syntax or format details beyond that, so the 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?

The description opens with a specific verb+resource ('Fetch one TechRadar author's public profile') and enumerates the returned content (name, job title, biography, social links, recent articles). It explicitly distinguishes itself from techradar_article, techradar_headlines, and techradar_news, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

It names the alternatives and the conditions that select them: techradar_article for one story's content, and techradar_headlines/techradar_news for current outlet feeds. This is explicit when-to-use guidance rather than inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.