Crawlora MCP

sportingnews_author

Read-only

Fetch one Sporting News US author's public profile, biography, photo, social links, and recent articles. Use sportingnews_article for one story.

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

Input Schema

Name	Required	Description	Default
`url`	No	Canonical sportingnews.com/us/author/<slug> URL; alternative to slug
`slug`	No	Author slug, e.g. anne-erickson

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

TDQS

A4.3/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, covering the safety profile. The description adds the scope of returned data (public profile, biography, photo, social links, recent articles), but with an output schema present, this is largely redundant. No additional behavioral details such as rate limits or auth needs are provided.

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 the core action and followed by a routing hint. No wasted words; every sentence earns its place.

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?

Given a simple fetch operation, 100% schema coverage, an existing output schema, and annotations covering safety, the description provides sufficient context: what it does, what it returns, and the alternative. Nothing essential is missing for correct invocation.

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 coverage is 100%, with clear descriptions for url and slug. The description does not add any parameter-level meaning beyond what the schema provides, so the baseline of 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 'author's public profile' with explicit contents (biography, photo, social links, recent articles). It distinguishes itself from the sibling article tool by noting 'Use sportingnews_article for one story.'

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?

Explicitly names the alternative tool sportingnews_article and the condition 'for one story', giving clear routing guidance. This is sufficient to choose between fetching an author profile and fetching a single article.

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?