Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_article

Retrieve a Sportskeeda article's public metadata and body paragraphs by supplying exactly one article slug or canonical URL. Use it to access clean article content via Crawlora MCP.

Instructions

Get a Sportskeeda article. Returns public article metadata and body paragraphs for a Sportskeeda article slug. Discovered slugs may contain case-preserving percent-encoded characters. A canonical Sportskeeda URL remains accepted for existing clients. Provide exactly one of slug or url; use /sportskeeda/sections and /sportskeeda/sitemaps for topic discovery.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape ("public article metadata and body paragraphs") and warns that slugs may contain case-preserving percent-encoded characters, but says nothing about auth requirements, rate limits, or error behavior. Decent but incomplete for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose and return content, followed by the encoding quirk and routing guidance. Every sentence contributes; no padding.

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?

No output schema exists, so the description correctly compensates by stating what is returned. Combined with the mutual-exclusivity rule and the percent-encoding caveat, an agent has enough to invoke it correctly; only auth/error behavior is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema by stating the two parameters are mutually exclusive ("exactly one of slug or url") — a oneOf constraint the schema does not encode, since both are optional and non-required.

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 ("Get a Sportskeeda article") and immediately scopes it as returning "public article metadata and body paragraphs." This distinguishes it from sibling resources like sportskeeda_video and sportskeeda_news by resource type, though it doesn't explicitly call out those 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?

Gives an explicit invocation constraint ("exactly one of slug or url") and routes the agent to sibling tools (/sportskeeda/sections and /sportskeeda/sitemaps) for the adjacent task of topic discovery. Clear context with no stated when-not exclusion beyond the mutual-exclusivity rule.

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

Deploy Server

Other Tools