Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_player_recent_matches

Read-only

Returns a CS2 player's newest BO3.gg matches (1 to 30, default 10) with the opponent, tournament, rounds, each map in order with whether the player's team won it, and the player's own line (rating, kills, deaths, assists, damage, first kills and deaths, trade kills and deaths, headshots, accuracy). Provide slug (for example donk); filter with opponent or tournament. Use it for recent form; use bo3_player_stats for windowed totals.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRequired slug of the team or the player, for example vitality or donk.
limitNoOptional number of newest matches 1 to 30, default 10. The upstream does not page past 30.
opponentNoOptional opposing team slug, for example natus-vincere, to list head-to-head matches only.
tournamentNoOptional tournament slug from bo3_tournaments, to list that event's matches only.

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

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds that only the newest matches are returned and that the player's own line is attached per map. It doesn't disclose rate limits, auth needs, or behavior for a slug that resolves to a team rather than a player, which is the main remaining ambiguity.

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 core action and the routing hint are front-loaded and the whole thing is one dense paragraph with no filler. The long enumeration of stat fields is somewhat redundant given an output schema exists.

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?

With a full output schema and read-only annotations, an agent has everything needed to call this correctly; the description fills in scope (newest matches) and the sibling comparison. Minor gap: no guidance on what happens when the slug is a team slug, which the schema explicitly permits.

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%, so the schema already documents limit (1-30, default 10, no paging past 30), opponent and tournament. The description largely restates those facts, adding only the concrete slug example (donk); baseline 3 is appropriate when the schema does the heavy lifting.

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 a CS2 player's newest BO3.gg matches) and immediately scopes the payload to opponent, tournament, rounds, per-map results and the player's stat line. An agent can distinguish it from bo3_player_stats or bo3_team_recent_matches without opening any 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?

"Use it for recent form; use bo3_player_stats for windowed totals" names the sibling alternative and the exact condition that selects each one. The slug/opponent/tournament guidance in the preceding sentence further pins down how to narrow results.

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