Crawlora MCP

space_author

Read-only

Fetch a Space.com author's public profile with job title, biography, and recent article items by slug or canonical url. Use space_article for one story or space_headlines for current headlines.

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

Input Schema

Name	Required	Description	Default
`url`	No	Canonical space.com/author/<slug> URL; alternative to slug
`slug`	No	Author slug, e.g. elizabeth-howell

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. elizabeth-howell"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical space.com/author/<slug> URL; alternative to slug"
```
First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds useful context by naming the returned profile fields, but says nothing about pagination, rate limits, or how many recent articles are returned, and the output schema already documents the return shape.

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, front-loaded with verb+resource, followed immediately by the sibling routing guidance. Zero waste, nothing buried.

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?

For a simple read-only profile fetch with 100% schema coverage and an output schema that captures the return values, the description omits nothing an agent needs to call it correctly: purpose, inputs, and alternatives are all covered.

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 both slug (with an example) and url. The description only restates that either can be used, adding no syntax or precedence rules beyond the structured fields. Baseline 3 is correct.

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 (Space.com author's public profile), enumerates the content (job title, biography, recent article items), and names the two siblings it is distinct from (space_article, space_headlines). An agent can differentiate it 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 to alternatives: space_article for a single story and space_headlines for current headlines. That names when to pick a sibling, though it doesn't restate the positive trigger ('use this when you need the author profile').

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?