Brawl Stars

Brawl Stars Player

brawl_stars_player

Read-onlyIdempotent

Brawl Stars official API — full profile for a player tag (#9LJ2YR9…): trophies, highest trophies, club, brawler count, 3v3 wins, solo/duo wins, and experience level.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tag": "#ABC123DEF"
    },
    "name": "brawl_stars_player"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	Yes

Output Schema

Name	Required	Description
`tag`	No	Player tag
`club`	No
`name`	No	Player name
`brawlers`	No
`expLevel`	No	Experience level
`trophies`	No	Total trophies
`expPoints`	No	Experience points
`duoVictories`	No	Duo match victories
`3vs3Victories`	No	3v3 match victories
`soloVictories`	No	Solo match victories
`highestTrophies`	No	Highest trophies reached
`bestRoboRumbleTime`	No	Best Robo Rumble time
`bestTimeAsBigBrawler`	No	Best Big Brawler time
`isQualifiedFromChampionshipChallenge`	No	Championship qualification status

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare that this is a read-only, idempotent, non-destructive, open-world operation. The description adds useful context about what profile fields are returned and that it uses the official API, but it does not mention auth requirements, rate limits, invalid-tag behavior, or whether data is live or cached.

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?

The description is a single front-loaded sentence that states the source, resource, parameter, and returned fields without wasted wording. Every listed field helps an agent understand the payload.

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?

An output schema exists, so the description need not explain return values in detail, and annotations cover safety and idempotency. The main remaining gap is the absence of usage guidance relative to sibling tools, but the core call context is otherwise complete.

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?

The schema has 0% description coverage for its single required parameter, so the description must carry meaning. It does this by naming the parameter as a player tag and showing the '#9LJ2YR9…' format, which is more than the bare string type in the schema.

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 clearly identifies the resource as a full Brawl Stars player profile for a given player tag and lists the profile fields returned. It does not explicitly contrast itself with siblings such as brawl_stars_player_battles or rankings, but the field list makes the scope distinguishable.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus the related battles, rankings, club, or brawler tools. The intended use is implied by 'full profile for a player tag,' but no alternatives or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Brawl Stars 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.