Crawlora MCP

tomsguide_author

Read-only

Fetch one Tom's Guide author's profile and one page of recent article links from a canonical author URL. Use tomsguide_article for a story's full content, or tomsguide_headlines and tomsguide_sections for outlet-wide browsing.

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": "tomsguide_author"
  }
}

Input Schema

Name	Required	Description
`url`	No	Canonical tomsguide.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-pritchard

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-pritchard"
```

addedInput schema / properties / url / description

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

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, open-web read. The description adds one useful behavioral detail, that the result is scoped to a single page of article links, but does not describe pagination beyond that, rate limits, or what an author profile contains.

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 sentences, no filler, and the scope ('one author, one page') is front-loaded before the sibling routing guidance.

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?

With an output schema present, return values need not be explained, and the annotations carry the safety profile. The description covers purpose, scope, and alternatives adequately; only minor behavioral detail (pagination behavior) is absent.

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 including the url-vs-slug alternative and page override precedence. The description adds no parameter detail beyond noting the canonical URL form, so the baseline 3 applies.

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 ('Fetch') and resource ('one Tom's Guide author's profile and one page of recent article links') with explicit scope ('from a canonical author URL'). An agent can distinguish it from tomsguide_article, tomsguide_headlines, and tomsguide_sections without opening any 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?

Explicitly routes the agent away from this tool: tomsguide_article for full story content, tomsguide_headlines and tomsguide_sections for outlet-wide browsing. The 'when to use this' case is implied by the fetch description rather than stated outright, so it falls just short of a full 5.

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.

Resources

Need Help?