Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_find_matches

Find recent public Dota 2 matches by hero lineup, filtering by up to five heroes on team A and/or team B and returning full Radiant and Dire lineups, winner, and requested side outcomes.

Instructions

OpenDota Dota 2 matches by hero lineup. Returns recent public Dota 2 matches in which the given heroes were on team A and/or team B, with both full lineups (radiant and dire), whether Radiant won, and which side the requested team A heroes were on and whether they won. Provide at least one hero id in total; each side takes up to 5 comma-separated hero ids from opendota-heroes. Unknown or repeated hero ids return an invalid-parameter error.

Input Schema

NameRequiredDescriptionDefault
team_aNoComma-separated hero ids (up to 5) that must be on team A
team_bNoComma-separated hero ids (up to 5) that must be on team B

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses what comes back (both full lineups, Radiant win flag, which side the team A heroes were on and whether they won) and the failure mode for unknown or repeated hero ids. Missing only auth/rate-limit or pagination context.

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 purpose before the return shape and the validation rules. Slightly dense in the middle sentence, but every clause carries information an agent needs.

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?

Only two flat parameters and no output schema, so the description has to describe the response — and it does, listing the fields returned. Nothing an agent needs to construct a call or interpret the result is missing, short of ordering/paging behavior.

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 baseline is 3. The description adds genuine value beyond the schema: it defines the at-least-one-hero-id requirement (which the schema's empty required list does not enforce), names opendota-heroes as the source of valid ids, and specifies the error on unknown or repeated ids.

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?

States a specific verb and resource: returns recent public Dota 2 matches filtered by hero lineup on team A and/or team B. The scope (recent, public, hero-filtered) implicitly distinguishes it from sibling lookups like opendota_match or opendota_pro_matches, but no sibling is named to make the distinction explicit.

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?

'Provide at least one hero id in total' is a valid-call constraint rather than a when-to-use rule, and hero ids must come 'from opendota-heroes'. The use case is implied clearly enough to act on, but there is no explicit exclusion or alternative (e.g., opendota_hero_matches for one hero) to steer selection.

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

Deploy Server

Other Tools