Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bo3_tournament_squads

Read-only

Returns each team's squad at a BO3.gg CS2 tournament as it played there: team and every player with nickname, name, photo, coach flag and stand-in flag. Provide slug from bo3_tournaments. Use it to see who played at an event, including substitutes; use bo3_team for the current roster.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRequired CS2 tournament slug from bo3_tournaments, for example pgl-masters-bucharest-2026.

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
Behavior3/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 genuinely useful behavioral context — that results are a historical, tournament-time snapshot including substitutes, not a current roster — but does not touch on coverage, empties, or pagination. Given annotation coverage, a 3 is fair.

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 is returned, then provenance and the sibling routing. No filler; every clause carries information.

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?

An output schema exists, so return values needn't be described; the single required parameter is fully documented in both schema and description, and the sibling alternative is named. Nothing an agent needs to call this 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 documents the slug with a source tool and an example. The description's 'Provide slug from bo3_tournaments' restates the schema rather than adding format or edge-case guidance, so baseline 3 applies.

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?

Specific verb ('Returns') plus specific resource ('each team's squad at a BO3.gg CS2 tournament') and an explicit data-scope list (nickname, name, photo, coach flag, stand-in flag). The 'as it played there' framing distinguishes it cleanly from roster-style siblings like bo3_team.

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?

States the use case ('see who played at an event, including substitutes') and names the alternative with the condition that selects it ('use bo3_team for the current roster'). It also tells the agent where the required slug comes from.

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