Crawlora MCP

opendota_league_match_ids

Read-only

Returns match IDs for one OpenDota league, including amateur leagues omitted by opendota_league_matches. Provide a positive league_id from opendota_leagues. An empty match_ids list is valid when a league has no matches; use opendota_match to fetch details for a returned ID.

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": {
      "league_id": "<league_id>"
    },
    "name": "opendota_league_match_ids"
  }
}

Input Schema

Name	Required	Description	Default
`league_id`	Yes	Required positive OpenDota league ID from opendota_leagues; this endpoint includes amateur leagues.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context beyond them: amateur-league coverage differences vs. a sibling, the empty-list-validity rule, and the downstream routing to opendota_match. It doesn't discuss rate limits or result ordering, so not 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.

Conciseness5/5

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

Four tight sentences, each earning its place: purpose/sibling differentiation first, then input requirement, then edge case, then next-step pointer. Front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and annotations, the description covers everything an agent needs: what it returns, valid input, edge case, and follow-up. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds value by restating the 'positive' constraint and the provenance ('from opendota_leagues'), reinforcing what the schema documents rather than just repeating the name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns match IDs for one OpenDota league') and immediately distinguishes itself from the closest sibling by noting it includes amateur leagues omitted by opendota_league_matches. An agent can pick this tool apart from opendota_league_matches without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to supply a positive league_id from opendota_leagues and to use opendota_match to fetch details for a returned ID, covering both input sourcing and next step. It also clarifies the edge case that an empty match_ids list is valid, removing ambiguity about an empty result.

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

All Crawlora MCP tools Inspect

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

Need Help?