Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_tournament_squads

Returns every CS2 team's tournament squad, including each player, coach, and stand-in, so you can see who actually played at a given event.

Instructions

BO3.gg CS2 tournament squads. Returns every team's squad at a CS2 tournament as it played there: team, and each player with nickname, name, photo, coach flag and stand-in flag. Use it to see who actually played, including substitutes.

Input Schema

NameRequiredDescriptionDefault
slugYesCS2 tournament slug from bo3-tournaments, for example pgl-masters-bucharest-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the load and does disclose the return shape: team plus each player's nickname, name, photo, coach flag and stand-in flag. It does not mention whether this requires a valid slug only from bo3-tournaments or how large the payload is, but the substantive data disclosure is solid for a read tool.

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?

Three short sentences, front-loaded with the resource identity, then the return shape, then the use case. No filler or repetition.

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?

Because there is no output schema, the description's enumeration of returned fields is what makes the tool callable with correct expectations. Combined with a fully documented single parameter, only minor gaps remain (payload size, slug sourcing is only in the schema).

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 single 'slug' parameter is documented in the schema with an example, so the description need not restate it. It adds no syntax or lookup guidance beyond the schema, which is the baseline case.

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 ('every team's squad at a CS2 tournament') and scopes it to how the squad actually played, which distinguishes it from sibling roster-ish tools like bo3_team or bo3_tournament_mvps. An agent can tell what it returns without 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 Guidelines4/5

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

Gives an explicit use case: 'see who actually played, including substitutes,' which tells the agent this is the historical/participation view rather than a current roster. It does not name an alternative sibling or state when NOT to use it, so it falls short of 5.

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