Crawlora MCP

standard_author

Read-only

One Evening Standard author's public profile: name, job title, bio, X/Twitter handle, and their recent articles.

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

Input Schema

Name	Required	Description	Default
`url`	No	Canonical standard.co.uk/author/<slug> URL; alternative to slug
`slug`	No	Author slug, e.g. nicholas-cecil

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.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / slug / description
```
Added value: +"Author slug, e.g. nicholas-cecil"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical standard.co.uk/author/<slug> URL; alternative to slug"
```
First observedOct 5, 2026

TDQS

A3.6/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 safety profile is covered. The description adds the shape of the payload (profile fields plus recent articles), which is useful context, but says nothing about pagination of the article list, how a missing/ambiguous author resolves, or error behavior.

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?

A single front-loaded sentence with zero filler; the resource identity comes first and the payload fields follow. Every word earns its place.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The only soft spot is that neither url nor slug is marked required in the schema and the description does not clarify that one must be supplied, but otherwise it is complete for a simple lookup tool.

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% and both parameters carry their own descriptions (url as canonical alternative to slug, slug with an example). The description adds no parameter meaning at all, so the baseline 3 for high-coverage schemas applies.

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?

The description names a specific resource (one Evening Standard author's public profile) and enumerates the returned fields (name, job title, bio, X/Twitter handle, recent articles), so an agent can immediately localize it among the standard_* family. It lacks an explicit verb and does not contrast itself against standard_article/news/headlines, so it stops short of a 5.

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?

Usage is only implied: the description reads as a profile lookup, which is self-evident for an 'author' tool. It gives no when-to-use vs alternatives (e.g. standard_article), no note that exactly one of url/slug should be provided, and no prerequisite or discovery guidance.

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?