Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_all_pages

Read-only

Lists page titles on one Liquipedia wiki with native namespace, prefix/range, redirect, language-link, page-size, protection, ordering and continuation filters. Use liquipedia_enums for namespace and closed filter values; preserve Liquipedia 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_all_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
aptoNoOptional source page title to stop enumeration at.
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
apdirNoOptional source ordering direction.
apfromNoOptional source page title to start enumeration from.
aplimitNoPage size from 1 through 500, or the string max; source default is 10.
apprefixNoOptional source page-title prefix.
apprtypeNoOptional repeatable page-protection type.
continueNoOptional global MediaWiki continuation value.
apmaxsizeNoOptional maximum page size in bytes; MediaWiki may disable this under miser mode.
apminsizeNoOptional minimum page size in bytes.
apprlevelNoOptional protection level; applies with apprtype.
apcontinueNoOptional native all-pages continuation token.
apprexpiryNoOptional protection-expiry filter.
apnamespaceNoOptional source namespace ID; discover IDs with liquipedia_enums.
apfilterredirNoOptional redirect filter.
apfilterlanglinksNoOptional language-link filter.
apprfiltercascadeNoOptional cascading-protection filter.

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

A3.5/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 profile is covered. The description adds the attribution obligation and the continuation/filter framing, but says nothing about result volume, continuation mechanics, or the miser-mode size caveat 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 sentences, front-loaded with the core action and scope, then the supporting directives. Dense but every clause maps to real capability; only the long filter enumeration verges on restating the schema.

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 17-parameter read-only listing tool with a full output schema and complete parameter descriptions, the description supplies the essentials: scope to one wiki, the enum lookup pointer, and the attribution requirement. Continuation/pagination behavior is the only notable omission.

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% across all 17 parameters, so the schema itself carries per-parameter meaning. The description only groups filters by category (namespace, prefix/range, redirect, language-link, page-size, protection, ordering, continuation), adding orientation but no syntax or format detail. Baseline 3 applies.

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 page titles") scoped to "one Liquipedia wiki", and enumerates the filter families it supports. It is clearly a bulk enumeration tool, distinguishable in spirit from search tools, though it does not name a specific sibling it replaces.

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 two concrete usage instructions: consult liquipedia_enums for namespace and closed filter values, and preserve Liquipedia attribution. It does not say when to choose this over liquipedia_prefix_search or liquipedia_search, which is the main routing decision an agent faces.

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