Crawlora MCP

bo3_team_recent_matches

Read-only

Returns a CS2 team's newest BO3.gg matches (1 to 30, default 10) with the opponent, tournament, rounds, each map in order and every player's line (rating, kills, deaths, assists, damage, first kills and deaths, trade kills and deaths, headshots, accuracy, equipment value). Provide slug (for example vitality); filter with opponent (a team slug) for head-to-head history or tournament (a bo3_tournaments slug). Date windows are not supported upstream. Use it for recent form; use bo3_match_history for results over a date range.

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

Input Schema

Name	Required	Description
`slug`	Yes	Required slug of the team or the player, for example vitality or donk.
`limit`	No	Optional number of newest matches 1 to 30, default 10. The upstream does not page past 30.
`opponent`	No	Optional opposing team slug, for example natus-vincere, to list head-to-head matches only.
`tournament`	No	Optional tournament slug from bo3_tournaments, to list that event's matches only.

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

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds valuable behavioral constraints — the 30-match hard cap and that date windows are not supported upstream. It stops short of describing pagination or error behavior, but the added upstream constraints are genuinely useful.

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?

Purpose and limit are front-loaded in the first clause, followed by filter guidance and the sibling alternative. It is dense but every clause carries information; minor length from the exhaustive field list.

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?

With an output schema, full parameter descriptions, and read-only annotations, the description fills the remaining gaps an agent needs: limit cap, unsupported date filtering, and the correct alternative tool. Nothing required to call it correctly 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 coverage is 100% and the schema already gives examples and the head-to-head semantics for opponent, so the description largely restates it. It reinforces that tournament takes a bo3_tournaments slug, but adds little beyond the structured fields, matching the baseline for high coverage.

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'), resource ('CS2 team's newest BO3.gg matches'), scope (1-30, default 10), and enumerates the returned fields, so an agent immediately understands what it produces. It is clearly distinct from date-range and player-scoped siblings.

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 routes the agent: 'Use it for recent form; use bo3_match_history for results over a date range.' It also explains when to apply the opponent and tournament filters (head-to-head, single event) and warns that date windows are unsupported upstream.

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.

Resources

Need Help?