Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_match

Fetch BO3.gg match details by slug, including teams, scores, winner, status, maps, tournament, streams, AI prediction, and key insights.

Instructions

BO3.gg match detail. Returns one BO3.gg match by slug: teams with scores and winner, status, best-of, tier, start and end time, tournament, stage and round, the maps played with scores, the site's AI prediction, live and recorded streams and the key-fact insights for each team. The slug comes from bo3-match-history.

Input Schema

NameRequiredDescriptionDefault
slugYesMatch slug from bo3-match-history, for example vitality-vs-natus-vincere-27-10-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. 'Returns one ... match' plus the full field enumeration makes clear this is a read-only single-entity fetch, but nothing is said about behavior for a nonexistent/invalid slug, whether historical matches expire, or any access constraints.

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?

Two sentences, front-loaded with what the tool returns, followed by the field inventory and then the input provenance. No filler; every clause conveys substantive information about the response shape.

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?

There is no output schema, so the description must describe return values, and it does so thoroughly across teams, scores, maps, tournament context, prediction, streams and insights. Minor gap: it doesn't say whether the payload is flat or nested or what happens on a missing match.

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% and the schema description already says the slug comes from bo3-match-history with a format example (vitality-vs-natus-vincere-27-10-2026). The description's mention of the same provenance adds nothing beyond the schema, so the baseline 3 applies.

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 one BO3.gg match by slug') and enumerates the payload: teams, scores, winner, status, best-of, tier, times, tournament, stage/round, maps, AI prediction, streams, key-fact insights. It is not explicitly differentiated from close siblings like bo3_match_games or bo3_match_players, but the field list implies the scope boundary.

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

Usage Guidelines4/5

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

Gives a concrete upstream dependency: 'The slug comes from bo3-match-history', which tells the agent where to get the required input. It does not state exclusions (e.g., when to prefer bo3_match_games for per-map/game detail instead), so it stops short of full when-not guidance.

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