Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_team

Fetch a BO3.gg team profile by slug to view roster, world rank, earnings, country, social links, and tournament achievements; optionally require a specific game.

Instructions

BO3.gg team profile. Returns a BO3.gg team profile by slug: name, acronym, game, world rank and rank change, country and region, founding date, six-month earnings, logo, social links, former names, the current roster (nickname, name, birthday, six-month rating) and the team's tournament achievements, newest first. Use game to insist on one game; a team of another game is not found.

Input Schema

NameRequiredDescriptionDefault
gameNoGame the team must belong to; one of cs2, valorant, lol, dota2, r6siege, mlbb
slugYesTeam slug, for example vitality

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the return payload in detail, notes that achievements are ordered newest first, and explains the game-filtering behavior that yields not-found results. It does not explicitly state read-only behavior, but the operational semantics are otherwise clear.

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 the tool's purpose and is appropriately sized for the amount of return-field detail. There is minor redundancy between 'BO3.gg team profile' and 'Returns a BO3.gg team profile by slug', but every sentence otherwise earns its place.

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 no output schema, the description does the necessary work of enumerating return fields and ordering. It is nearly complete for calling the tool correctly, with the main gap being no explicit routing guidance to sibling tools that cover team statistics, rankings, or recent matches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the consequence of `game` (a team of another game is not found) and by framing `slug` as the identifier for the team profile.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: returns a BO3.gg team profile by slug, and enumerates the profile contents. It clearly distinguishes this as a profile lookup rather than a list/search, though it does not explicitly name sibling tools like bo3_team_stats or bo3_team_rankings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives useful guidance for the optional `game` parameter ('Use `game` to insist on one game; a team of another game is not found'), but does not explain when to use this tool versus sibling tools such as bo3_team_stats, bo3_team_recent_matches, or bo3_team_rankings.

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