Crawlora MCP

sportskeeda_author

Read-only

Look up a Sportskeeda author's public profile and recent story links. Provide one canonical author slug or /author/ URL.

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

Input Schema

Name	Required	Description	Default
`url`	No	Canonical Sportskeeda /author/<slug> URL; alternative to slug
`slug`	No	Sportskeeda author slug, e.g. sripad

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: +"Sportskeeda author slug, e.g. sripad"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical Sportskeeda /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 and scope profile is covered. The description adds that the profile is public and that recent story links are returned, which is modest additional context, but nothing about rate limits, auth, or failure modes.

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 short sentences, front-loaded with the purpose and followed by the input constraint. 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, the description needn't explain return values, and annotations cover the safety profile. It is nearly complete, but the lack of any routing versus the overlapping sportskeeda_profile sibling is the one remaining gap.

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 both parameters are already documented in the schema. The description reinforces that slug and URL are alternatives ('Provide one canonical ... or ...'), which adds slight value, but the baseline for full coverage is 3.

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?

States a specific verb and resource: 'Look up a Sportskeeda author's public profile and recent story links.' This is clearly an author-centric lookup, distinguishable from sportskeeda_article. However, it does not differentiate itself from the sibling sportskeeda_profile, which likely overlaps in purpose.

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?

The description tells the agent how to supply input ('Provide one canonical author slug or /author/<slug> URL') but gives no explicit when-to-use versus alternatives such as sportskeeda_article or sportskeeda_profile. Usage is implied rather than stated, so a 3 is appropriate.

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?