Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_match_games

Read-only

Returns the maps of one BO3.gg match with round-by-round results: per map the map name, duration in seconds, final score, per-half side results and every round (number, duration, end reason, winning side, running score). Provide match_id, the id of a bo3_match_history row. A match with no maps yet returns an empty list. Use it for round-level detail; use bo3_match_players for player statistics.

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": {
      "match_id": "<match_id>"
    },
    "name": "bo3_match_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYesRequired numeric BO3 match id (the id field of bo3_match_history rows).

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declaring safety, the description adds the useful behavioral edge case: 'A match with no maps yet returns an empty list.' This preempts confusion over empty results. It doesn't mention performance, rate limits, or auth, but those are less critical here.

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 description is front-loaded with purpose, then parameters, edge case, and alternative. Dense but every sentence carries information; the field enumeration is long but purposeful. Slightly verbose in the round-detail listing.

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?

With an output schema and annotations present, the description covers purpose, param provenance, edge case, and routing. It leaves out the bo3_match parent sibling relationship, but the core needs for correct invocation are all present.

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?

Schema coverage is 100%, so the parameter is fully documented in structured data. The description's note that match_id is a bo3_match_history id matches the schema and adds only a little provenance context. Baseline 3 is appropriate.

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?

The description uses a specific verb ('Returns the maps') plus a precise resource scope ('of one BO3.gg match with round-by-round results') and enumerates the exact per-map fields. It separates itself from bo3_match_players explicitly, so an agent can choose it without opening the 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?

It explicitly states 'Use it for round-level detail; use bo3_match_players for player statistics', naming both the suitable case and the alternative with the condition that selects it. It also clarifies the match_id must come from a bo3_match_history row, giving the entry point.

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

All Crawlora MCP toolsInspect
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