Crawlora MCP

stuff_author

Read-only

Fetch a Stuff New Zealand author's public profile and recent stories. Use stuff_article for one story or stuff_news and stuff_headlines for current 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": "stuff_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Canonical stuff.co.nz/authors/<slug> URL; alternative to slug
`slug`	No	Author slug, e.g. damien-venuto

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. damien-venuto"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical stuff.co.nz/authors/<slug> URL; 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 safety profile is covered. The description adds that it returns a public profile plus recent stories, but says nothing about authentication, rate limits, or result limits — adequate but not rich given annotations carry the main load.

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 tight sentences, purpose front-loaded, alternative routing second. No filler.

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 needn't be described, and the description covers purpose and alternatives. Minor gap: it doesn't clarify the url-vs-slug requirement, but the schema covers that.

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 (url, slug) are documented there including the url-as-alternative note. The description adds no parameter syntax or selection guidance beyond the schema, so 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 ('Stuff New Zealand author's public profile and recent stories'), which precisely distinguishes it from the article/news/headlines siblings.

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 to alternatives: 'Use stuff_article for one story or stuff_news and stuff_headlines for current articles.' This gives clear when-to-use-else context, though it doesn't state a hard exclusion or precondition for using this tool itself.

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?