Crawlora MCP

bo3_match

Read-only

Returns one BO3.gg match by slug: teams with scores and winner, status, best-of, tier, times, tournament, stage and round, the maps played with scores, the site's AI prediction, streams and key-fact insights per team. Provide slug from bo3_match_history. Use it for a single match's context; use bo3_match_players for player statistics and bo3_team for rosters.

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": {
      "slug": "<slug>"
    },
    "name": "bo3_match"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Required match slug from bo3_match_history, for example vitality-vs-natus-vincere-27-10-2026.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds that the payload includes derived editorial data (the site's AI prediction, streams, key-fact insights), which tells the agent the response is enriched rather than raw. It does not mention rate limits, freshness/caching, or behavior for unknown slugs, which keeps it below 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.

Conciseness4/5

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

Front-loaded with purpose, then the return-field inventory, then the sibling routing, so the most decision-relevant content comes first. The middle enumeration is long but each item (maps, prediction, streams, insights) is a genuine payload component, so little is wasted; only the run-on structure costs a point.

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?

Single required parameter, output schema present, and annotations cover safety, so the description need only frame scope and routing — which it does. Nothing essential to correct invocation is missing; only edge behavior (invalid or stale slug) is unstated.

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 description coverage is 100% and the single parameter is documented with an example in the schema, so the baseline is 3. The description adds provenance that the schema lacks in spirit — the slug must come from bo3_match_history — which meaningfully reduces the chance of a fabricated slug and lifts it above baseline.

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 one BO3.gg match by slug') and then enumerates the returned content: teams/scores/winner, status, best-of, tier, times, tournament, stage and round, maps with scores, AI prediction, streams and per-team insights. An agent can distinguish it from bo3_match_games, bo3_match_players and bo3_match_history without opening a 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 where the slug comes from ('Provide slug from bo3_match_history') and routes the agent away: 'use bo3_match_players for player statistics and bo3_team for rosters', while this tool is 'for a single match's context'. Both the entry condition and the sibling alternatives are named.

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.