Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_article

Read-only

Fetch a public Sportskeeda article by host-free path slug or canonical HTTPS URL. Use sportskeeda_news for news cards, sportskeeda_page_data for page metadata, or sportskeeda_wiki_article for Wiki content.

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_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical Sportskeeda article URL; alternative to slug
slugNoSportskeeda article path without host; preferred over url

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Sportskeeda article path without host; preferred over url"
    • addedInput schema / properties / url / description
      Added value: +"Canonical Sportskeeda article URL; alternative to slug"
  2. First observed

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 and external-network profile is known. The description adds that the article must be public and that the slug should omit the host, but says nothing about rate limits, redirect handling, or failures on private/paywalled articles, and there is an output schema covering return values.

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: the first front-loads what the tool does and the accepted identifier forms, the second routes to the correct siblings. No wasted words.

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 the annotations cover the safety profile. It is largely complete, though a note on what happens with non-public or malformed input would close the 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 coverage is 100% and the schema itself labels url as an alternative to slug and slug as preferred over url. The description only restates that both forms are accepted, adding no format or precedence detail beyond what the schema provides, 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 (public Sportskeeda article) and specifies the two accepted identifiers (host-free path slug or canonical HTTPS URL). It also names the sibling tools it is not, so an agent can distinguish it immediately.

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 sportskeeda_news, sportskeeda_page_data, and sportskeeda_wiki_article for their respective content types, which gives clear negative guidance. It doesn't state positive usage conditions beyond the identifier formats, but the exclusions are strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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