Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_team_stats

Read-only

Returns one statistics view of a BO3.gg team over a day range (default 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 economy level) or map-pool (maps picked and banned). Provide slug (for example vitality), kind and optional from/to days. Use it to compare teams or analyse one team's round profile; use bo3_player_stats for individual players.

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_team_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional last day, YYYY-MM-DD. Default: today (UTC).
fromNoOptional first day, YYYY-MM-DD. Default: six months before to.
kindNoOptional view: general (default), advanced, accuracy, economy or map-pool.
slugYesRequired team slug, for example vitality.

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

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

Annotations already cover readOnlyHint and openWorldHint, so the description's additional value is in detailing the default time range (last six months) and the content of each view. It does not mention rate limits or auth requirements, but for a read-only stats tool with clear schema this is sufficient.

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 and is reasonably compact. It is a single long sentence that packs multiple details but remains readable; could be split for slightly better structure.

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 tool's complexity (multiple view types, date range) and the presence of a rich output schema, the description covers what is necessary: required parameters, defaults, available views, and a sibling tool alternative. Nothing essential is missing.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description repeats the parameter names and adds an example slug ('vitality') and default range, but adds little beyond what the schema provides.

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 ('Returns') and resource ('statistics view of a BO3.gg team') and enumerates the available view types. Distinguishes itself from the sibling bo3_player_stats tool explicitly, making it easy for an agent to select correctly.

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?

Provides clear usage context ('compare teams or analyse one team's round profile') and names an alternative for player-level stats. However, it does not explicitly rule out other bo3_* team-related tools (e.g., bo3_team_rankings), leaving some inference required.

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