Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_wiki_pages

Search and paginate Sportskeeda Wiki catalog pages by project, using path_slug for article links. total_items shows record count; ignore mislabelled total_pages.

Instructions

Search and paginate Sportskeeda Wiki pages. Returns catalog pages for one Wiki project. Use path_slug as the preferred host-free slug for sportskeeda-wiki-article. total_items is the record count; the upstream field named total_pages is mislabelled and does not mean page count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based catalog page
sortNoSort direction
wikiYesProject slug returned by sportskeeda-wiki-options
limitNoItems per page
searchNoTitle or page search text; sent upstream as searchText
sort_byNoCatalog field to sort by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/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 behavioral burden. It usefully discloses a return-field caveat ('the upstream field named total_pages is mislabelled and does not mean page count', total_items is the record count), which is genuine signal. However, it says nothing about auth needs, pagination limits, or the read-only nature beyond the implicit 'Search'.

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?

Three sentences, front-loaded with purpose and scope, and each carries information (scope, routing hint, field caveat). The path_slug sentence is slightly awkward and refers to a non-param, but the text is otherwise efficient.

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?

For a search/paginate tool with a fully documented schema and no output schema, the description compensates for the missing output schema by flagging the misleading total_pages field. It stops short of describing search behavior or what a catalog page contains, but the essentials for correct invocation are present.

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 all six parameters, making 3 the baseline. The description adds little parameter-level meaning, and its mention of 'path_slug' (which is not a param in this schema) is potentially confusing rather than clarifying.

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?

The description states a specific verb (search/paginate) and resource (Sportskeeda Wiki pages) and scopes it to 'one Wiki project' via the required wiki param. It differentiates itself somewhat from siblings by framing output as catalog pages, though it never explicitly contrasts against siblings like sportskeeda_wiki_categories or sportskeeda_wiki_options.

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?

There is an implied usage hint ('Use path_slug as the preferred host-free slug for sportskeeda-wiki-article'), which loosely routes the agent toward a sibling, but no explicit when-to-use or when-not-to-use guidance. Given a dense set of sportskeeda_wiki_* siblings, the agent gets only partial routing help.

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