Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_prefix_search

Read-only

Suggests matching page titles from a search prefix using the source's prefix-search operation. Use it for typeahead-like page discovery; it returns source ranking, namespace, offset, page-size, and continuation controls. Discover namespaces with liquipedia_enums and 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>",
      "pssearch": "<pssearch>"
    },
    "name": "liquipedia_prefix_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
pslimitNoPage size from 1 through 500, or the string max; source default is 10.
continueNoOptional global MediaWiki continuation value.
psoffsetNoOptional non-negative source result offset.
pssearchYesRequired source prefix-search string.
psprofileNoOptional source prefix-search ranking profile.
psnamespaceNoRepeatable source namespace IDs as numbers, or the string * for all namespaces.

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.6/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 a genuine operational requirement (preserve Liquipedia attribution) and notes the source default page size, but says nothing about rate limits, result caps, or failure behavior when wiki or namespace inputs are invalid.

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 plus a short trailing instruction, with purpose front-loaded before usage and prerequisites. No filler, though the clause enumerating ranking/offset/page-size is the least load-bearing part.

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?

An output schema exists and the input schema is fully documented, so return-value detail is unnecessary. The description covers purpose, usage context, namespace prerequisite, and an attribution obligation, leaving only sibling differentiation as a minor 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 description coverage is 100%, so the schema already defines all seven parameters, including the 1-500/max page size and the repeatable namespace IDs. The description's mention of ranking, namespace, offset, page-size, and continuation is framed as returned data and largely restates inputs, adding little new meaning and slightly blurring inputs versus outputs.

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: suggests matching page titles from a search prefix using the source's prefix-search operation, and frames it as typeahead-style discovery. That is clearly distinct from a full-text search, though it never names liquipedia_search or liquipedia_all_pages to make the boundary explicit.

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 a concrete usage condition (typeahead-like page discovery) and a prerequisite step (discover namespaces with liquipedia_enums). It stops short of saying when not to use it, e.g. for full-text matches or complete listings, so the alternative selection remains partly inferred.

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