Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_category_members

Read-only

Lists pages in one wiki category with page IDs, titles, member types, sort fields, and continuation. Use a category name or page ID with a wiki slug; preserve source attribution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wiki": "<wiki>"
    },
    "name": "liquipedia_category_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
cmdirNoOptional direction for the selected source sort.
cmendNoOptional timestamp end bound; only valid with cmsort=timestamp.
cmpropNoOptional repeatable metadata fields to include.
cmsortNoOptional source sort key.
cmtypeNoOptional repeatable category member type filter.
cmlimitNoPage size from 1 through 500, or the string max; source default is 10.
cmstartNoOptional timestamp start bound; only valid with cmsort=timestamp.
cmtitleNoCategory title including the Category: prefix; mutually exclusive with cmpageid.
cmpageidNoOptional category page ID; mutually exclusive with cmtitle.
continueNoOptional native global MediaWiki continuation value.
cmcontinueNoOptional native category-members continuation value.
cmnamespaceNoRepeatable source namespace IDs, or the string * for all namespaces.
cmendhexsortkeyNoOptional ending hexadecimal category sort key; only valid with cmsort=sortkey.
cmstarthexsortkeyNoOptional starting hexadecimal category sort key; only valid with cmsort=sortkey.
cmendsortkeyprefixNoOptional ending human-readable sort-key prefix; only valid with cmsort=sortkey.
cmstartsortkeyprefixNoOptional starting human-readable sort-key prefix; only valid with cmsort=sortkey.

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. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint; the description usefully adds that continuation is exposed and that source attribution must be preserved, but it does not discuss pagination flow or limits beyond what the schema states.

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?

Two tight sentences, front-loaded with the purpose and the invocation rule; the field list slightly duplicates the output schema but is short enough not to be wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 parameters, full schema coverage, and an output schema, the description does the minimum: it identifies the required wiki slug and attribution duty but gives no guidance on sorting, namespaces, or continuation chaining.

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 every parameter is already documented, including the cmtitle/cmpageid mutual exclusion; the description merely restates 'category name or page ID' without adding format or sort-key guidance.

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 ('Lists pages in one wiki category') plus the returned fields, which separates it from liquipedia_categories, but it does not name that sibling explicitly.

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?

Gives invocation guidance ('Use a category name or page ID with a wiki slug') and an attribution obligation, but never says when to pick this over liquipedia_categories, liquipedia_all_pages, or liquipedia_prefix_search.

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