Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_recent_changes

Read-only

Lists recent changes on one Liquipedia wiki with source time bounds, namespace/tag/type/visibility filters, ordering, page-size controls, and native continuation. User identities and edit-comment text are omitted. Discover tags with liquipedia_tags and namespace IDs with liquipedia_enums; 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_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
rcdirNoOptional source ordering direction.
rcendNoOptional source timestamp upper bound.
rctagNoOptional change tag name; discover current tags with liquipedia_tags.
rcpropNoOptional repeatable source metadata fields; user identity, free-text comment, and permission-restricted patrolled properties are not returned.
rcshowNoOptional repeatable source visibility filters.
rcslotNoOptional source slot filter; main is the only supported slot.
rctypeNoOptional repeatable source change type filter.
rclimitNoPage size from 1 through 500, or the string max; source default is 10.
rcstartNoOptional source timestamp lower bound.
rctitleNoOptional page title filter.
continueNoOptional global MediaWiki continuation token.
rctoponlyNoReturn only latest revisions when true.
rccontinueNoOptional native recent-changes continuation token.
rcnamespaceNoRepeatable 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.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world, so the bar is lower, and the description still adds non-obvious behavior: user identities and edit-comment text are omitted from results, native continuation is supported, and Liquipedia attribution must be preserved. It stops short of describing pagination semantics (rclimit vs continue interplay) or result shape, which keeps it off a 5.

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 the core action and scope, then the privacy/behavioral caveats, then prerequisite and attribution notes. Dense but every sentence carries distinct information; the parameter grouping in sentence one is the only slightly redundant 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?

For a 15-parameter read tool with a full output schema, the description covers scope, filter families, continuation, omitted fields, prerequisite lookups, and attribution. The main residual gap is any hint about how to combine rclimit with the two continuation tokens, which an agent may need to paginate correctly.

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%, so every parameter is already documented in the input schema, and the description only groups them ('source time bounds, namespace/tag/type/visibility filters, ordering, page-size controls'). That summary adds orientation but no per-parameter meaning beyond the schema, so 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?

The description gives a specific verb and resource ('Lists recent changes on one Liquipedia wiki') and enumerates the dimensions the listing can be shaped by. It does not directly contrast with look-alike siblings such as bo3_player_recent_matches, but the Liquipedia scope plus the pointer to liquipedia_tags/liquipedia_enums makes the boundary readable.

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?

The description gives prerequisite routing ('Discover tags with liquipedia_tags and namespace IDs with liquipedia_enums') which is genuinely useful before calling, and an attribution obligation. It does not say when to choose this over a different Liquipedia listing tool or when it is the wrong tool, so guidance is implied rather than complete.

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