Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_team_stats

BO3.gg team statistics. Returns one statistics view of a BO3.gg team over a day range (default: the last six months): general (match, game, round and kill totals), advanced (CT/T, pistol, eco, force and full-buy round records)…

Instructions

BO3.gg team statistics. Returns one statistics view of a BO3.gg team over a day range (default: the last six months): general (match, game, round and kill totals), advanced (CT/T, pistol, eco, force and full-buy round records), accuracy (hits and damage by hit group), economy (win rate by own and enemy economy level) or map-pool (maps picked and banned). General views fill stats; the other views fill rows.

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD; defaults to today (UTC)
fromNoFirst day, YYYY-MM-DD; defaults to six months before to
kindNoStatistics view; one of general, advanced, accuracy, economy, map-pool; defaults to general
slugYesTeam slug, for example vitality

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that this is a read that returns statistics, states the default day range (last six months), and — importantly, since there is no output schema — explains that general views populate `stats` while other views populate `rows`. It does not mention error behavior for unknown slugs or any rate limits.

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 the resource identity, then a single dense sentence that enumerates the views and closes with the return-shape mapping. Every clause carries information; slightly long but no filler.

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?

For a read-only stats tool with no output schema, the description covers the critical unknowns: view semantics, default time window, and which response field each view fills. Minor remaining gap is guidance on the parenthetical team identification path (only `slug` in schema) and behavior on unknown teams.

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 goes beyond the schema by explaining the substantive content of each enum value for `kind` (what 'advanced', 'accuracy', 'economy', 'map-pool' actually contain) and reinforces the six-month default for the date range, which the schema only states implicitly via the `from` default.

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 resource (BO3.gg team statistics) and then enumerates exactly what each of the five views returns, including the granular metrics (CT/T, pistol, eco, hit group damage, pick/ban maps). An agent knows precisely the shape of the data this tool produces before 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 Guidelines3/5

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

The description guides selection among the `kind` values, which is useful, but says nothing about when to use this versus the many sibling BO3 tools (bo3_team, bo3_team_recent_matches, bo3_player_stats, bo3_economy_baseline). No when-not or alternative-routing guidance is provided.

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