Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_match_games

Retrieve every map and round-by-round result for a BO3.gg match by match_id, including scores, sides, durations, and end reasons; returns an empty list when maps are not yet available.

Instructions

BO3.gg esports match maps with round-by-round results. Returns the maps of one BO3.gg match with round-by-round results: for each map the number, map name, state, start, duration in seconds, final score, per-half side results (CT or T score, overtime) and every round with its number, duration, end reason, winning side and running score. A match with no maps yet returns an empty list.

Input Schema

NameRequiredDescriptionDefault
match_idYesNumeric BO3 match id (the id of a bo3-match-history row)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a strong job explaining the returned data, including map fields and round-by-round details. It also discloses the edge case that a match with no maps returns an empty list, though it does not explicitly state that the operation is read-only.

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?

The purpose is front-loaded, and the detailed field enumeration is useful because there is no output schema. The opening sentence is somewhat redundant with the second, but overall the description remains dense and purposeful.

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?

Given the lack of an output schema, the description supplies the necessary return-shape details, including per-map fields and round-level fields. It also covers the empty-list edge case, leaving little ambiguity for an agent preparing to call the tool.

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 single match_id parameter is fully described in the schema as a numeric BO3 match id from a bo3-match-history row. The description adds little beyond that, so the high schema coverage justifies the baseline score.

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 states a specific result: it returns the maps of one BO3.gg match with round-by-round results. That clearly distinguishes a map-level round-detail tool from match-level or player-level siblings, though it does not explicitly name an alternative sibling such as bo3_match.

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

Usage Guidelines2/5

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

The description establishes the scope as one match but gives no explicit guidance on when to use this tool versus bo3_match, bo3_match_history, or other BO3.gg match-related tools. Usage is inferable from the purpose, but there are no stated alternatives or exclusion cases.

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