Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_search

Read-only

Searches page titles or text on one Liquipedia wiki and returns matching page IDs, titles, snippets, page links, and native continuation. Use a wiki slug and search text; source namespace and query-dependent and query-independent ranking profiles are supported. Preserve CC BY-SA 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>",
      "q": "<q>"
    },
    "name": "liquipedia_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesRequired MediaWiki search query.
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
srinfoNoOptional repeatable search metadata fields.
srpropNoOptional repeatable search-result fields.
srsortNoOptional native MediaWiki search sort mode.
srwhatNoOptional MediaWiki search mode.
srlimitNoPage size from 1 through 500, or the string max; source default is 10.
continueNoOptional native MediaWiki continuation token from the prior response.
sroffsetNoOptional source offset; use the returned continue.sroffset when paging.
srinterwikiNoInclude interwiki results when the source wiki provides them.
srnamespaceNoRepeatable source namespace IDs, or the string * for all namespaces.
srqdprofileNoOptional source query-dependent ranking profile.
srqiprofileNoOptional source query-independent ranking profile.
srenablerewritesNoAllow the source search backend to rewrite the query.

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
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the description does not need to repeat safety basics. It adds useful behavioral context by noting that results include page IDs, titles, snippets, page links, and native continuation, and by stating the CC BY-SA attribution requirement. It stops short of explaining rate limits, authentication, or pagination mechanics in more detail.

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?

The description is three sentences and front-loads the primary search purpose before covering supported features and attribution. It is generally efficient, though the phrase 'source namespace and query-dependent and query-independent ranking profiles are supported' is dense and largely mirrors schema fields rather than adding unique value.

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 14-parameter tool with full schema coverage, an existing output schema, and annotations covering safety, the description provides enough orientation: source wiki, required search inputs, supported ranking/namespace features, return fields, continuation, and attribution obligation. The main omission is guidance on selecting this tool over similar Liquipedia search or listing tools, but otherwise it is sufficiently complete.

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 14 parameters thoroughly. The description adds only a light layer of meaning by naming the wiki slug, search text, namespace support, and ranking profile support, but does not clarify the usage of srlimit, sroffset, continue, srwhat, srinfo, or srprop beyond what the schema already says. Baseline 3 is appropriate.

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 first sentence states a specific verb and resource: search page titles or text on one Liquipedia wiki, returning concrete fields. It is clear enough to distinguish from list-style or page-detail siblings by scope and search behavior, though it does not explicitly name an alternative such as liquipedia_prefix_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs the agent to use a wiki slug and search text, but that is parameter guidance rather than when-to-use guidance. It gives no explicit conditions for choosing this search over liquipedia_prefix_search, liquipedia_all_pages, or other siblings, and no when-not-to-use exclusions.

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