Skip to main content
Glama
Archers007

Liquipedia MCP

by Archers007

List esports matches

list_matches

Retrieve esports match schedules and results from Liquipedia. Filter by wiki, team, tournament, or date to get upcoming and completed matches with scores and stream links.

Instructions

Fetch matches (schedules + results) for a wiki. Filter by team/opponent, tournament, or date. Returns upcoming and completed matches with scores, opponents, tournament, and stream URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate condition, e.g. '>2024-01-01' or '<2025-01-01'.
wikiYesLiquipedia wiki(s) to query, e.g. 'valorant', 'counterstrike', 'dota2'. Pipe-separate multiple wikis: 'valorant|counterstrike'.
limitNoMax rows to return (default 20).
orderNoSort order (default 'date DESC').
queryNoComma-separated list of fields to return (projection), e.g. 'pagename,date,opponent'.
opponentNoTeam name that must appear in the match, e.g. 'Shopify Rebellion'.
conditionsNoRaw Liquipedia condition string, e.g. '[[opponent::Team A]] AND [[date::>2024-01-01]]'. Combined (AND) with any structured filters. Use OR/AND and [[field::value]] syntax.
tournamentNoFilter to a specific tournament name.
Behavior3/5

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

No annotations are provided, so the description bears full burden. It mentions returning upcoming and completed matches with specific fields, but does not disclose rate limits, auth needs, error conditions, or pagination behavior. It is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with purpose and filters, and includes return value hints. No unnecessary words; every sentence adds value.

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?

Given 8 parameters and no output schema, the description covers high-level purpose and return fields, but lacks details on how filters combine, default limits, or the 'conditions' parameter. It is adequate but could be more 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?

The schema description coverage is 100%, so baseline is 3. The description adds minor context about which filters are available (team/opponent, tournament, date) and what is returned, but does not significantly enhance parameter understanding beyond the schema.

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 clearly states the tool fetches matches with filters, using specific verb 'Fetch' and resource 'matches'. However, it does not differentiate from sibling tools like 'query' or 'list_standings', missing some sibling distinction.

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?

It lists filters but lacks explicit guidance on when to use this tool versus alternatives. No 'when to use' or 'when not to use' is provided; usage is implied through the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Archers007/LiqMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server