Crawlora MCP

opendota_pro_matches

Read-only

Returns professional Dota 2 match results with match IDs, teams, league, start time, duration, scores, winner and series details. OpenDota returns up to 100 rows per page. Optionally provide less_than_match_id as a positive match ID to fetch older results, then use next_less_than_match_id from the response for the next page; an empty cursor page ends history, while an empty unfiltered page is an upstream data gap. This is not an upcoming schedule. Use opendota_live for games currently in progress or opendota_match for a detailed result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendota_pro_matches"
  }
}

Input Schema

Name	Required	Description	Default
`less_than_match_id`	No	Optional positive OpenDota match ID cursor; return matches with lower IDs.

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

A5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the 100-row page cap, the cursor pagination flow, the meaning of an empty cursor page (end of history) versus an empty unfiltered page (upstream data gap), and warns this is not an upcoming schedule. That is unusually rich behavioral context that annotations alone would not convey.

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 sentences, all front-loaded with purpose first, then pagination semantics, then the negative scoping ('not an upcoming schedule') and alternatives. Every sentence carries distinct information with no repetition.

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?

An output schema exists, so return-value structure needn't be spelled out, and the description already covers pagination termination, edge cases, and sibling routing. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

With 100% schema coverage the baseline would be 3, but the description adds real value: it explains the cursor is a positive match ID that fetches older results and that next_less_than_match_id from the response should be used for the next page. This page-chaining semantics goes beyond the schema's terse cursor note.

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 professional Dota 2 match results') and enumerates the returned fields (match IDs, teams, league, start time, duration, scores, winner, series details). It also explicitly distinguishes itself from opendota_live and opendota_match, so an agent can select it without opening siblings.

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 'This is not an upcoming schedule' and routes to opendota_live for in-progress games and opendota_match for detailed results. Both when-not and alternatives are named, leaving nothing to inference.

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?