Skip to main content
Glama

Brawl Stars

by io.github.pipeworx-io

Player

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoPlayer tag
clubNo
nameNoPlayer name
brawlersNo
expLevelNoExperience level
trophiesNoTotal trophies
expPointsNoExperience points
duoVictoriesNoDuo match victories
3vs3VictoriesNo3v3 match victories
soloVictoriesNoSolo match victories
highestTrophiesNoHighest trophies reached
bestRoboRumbleTimeNoBest Robo Rumble time
bestTimeAsBigBrawlerNoBest Big Brawler time
isQualifiedFromChampionshipChallengeNoChampionship qualification status

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "tag": "#ABC123DEF"
+  },
+  {
+    "tag": "#2P8YQ0RC9"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "3vs3Victories": {
+      "description": "3v3 match victories",
+      "type": "number"
+    },
+    "bestRoboRumbleTime": {
+      "description": "Best Robo Rumble time",
+      "type": "number"
+    },
+    "bestTimeAsBigBrawler": {
+      "description": "Best Big Brawler time",
+      "type": "number"
+    },
+    "brawlers": {
+      "items": {
+        "properties": {
+          "gadgets": {
+            "description": "Gadgets list",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "highestTrophies": {
+            "description": "Highest brawler trophies",
+            "type": "number"
+          },
+          "id": {
+            "description": "Brawler ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Brawler name",
+            "type": "string"
+          },
+          "power": {
+            "description": "Brawler power level",
+            "type": "number"
+          },
+          "rank": {
+            "description": "Brawler rank",
+            "type": "number"
+          },
+          "starPowers": {
+            "description": "Star powers list",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "trophies": {
+            "description": "Brawler trophies",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "club": {
+      "properties": {
+        "name": {
+          "description": "Club name",
+          "type": "string"
+        },
+        "tag": {
+          "description": "Club tag",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "duoVictories": {
+      "description": "Duo match victories",
+      "type": "number"
+    },
+    "expLevel": {
+      "description": "Experience level",
+      "type": "number"
+    },
+    "expPoints": {
+      "description": "Experience points",
+      "type": "number"
+    },
+    "highestTrophies": {
+      "description": "Highest trophies reached",
+      "type": "number"
+    },
+    "isQualifiedFromChampionshipChallenge": {
+      "description": "Championship qualification status",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Player name",
+      "type": "string"
+    },
+    "soloVictories": {
+      "description": "Solo match victories",
+      "type": "number"
+    },
+    "tag": {
+      "description": "Player tag",
+      "type": "string"
+    },
+    "trophies": {
+      "description": "Total trophies",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and safe behavior. The description adds value by enumerating the exact return data (trophies, club, brawler count, wins, experience level), giving the agent a clear picture of the response shape beyond the structured hints. No contradictions.

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?

A single, front-loaded sentence that conveys the API, the operation, the parameter format, and the key return fields. No filler or redundant content.

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?

This is a simple one-parameter read-only tool with a rich output schema and comprehensive annotations. The description covers the essential return content and parameter meaning. It could mention error behavior (e.g., invalid tag) but that's a minor gap.

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 input schema has zero description for the 'tag' parameter, so the description carries the burden. It clarifies the parameter with a real example (#9LJ2YR9…) and states that it's a Brawl Stars player tag, effectively compensating for the sparse schema.

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?

The description clearly specifies the action (retrieving a full profile) and resource (a Brawl Stars player tag), and lists concrete fields returned. It distinguishes itself from siblings like player_battles and rankings_players by focusing on overall profile stats.

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?

The description implies when to use it (when a player's full profile is needed) but does not explicitly state exclusions or name alternative tools. The field list provides implicit differentiation, but no direct guidance about when not to use this tool.

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

All Brawl Stars toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation2/5

The set mixes a general data-querying platform (Pipeworx) with a small Brawl Stars API wrapper. Within the Pipeworx cluster, ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim have overlapping lookup behavior, and the five polymarket_* tools cover similar prediction-market ground. The Brawl Stars tools are distinct but dwarfed, making the overall purpose confusing.

Naming Consistency3/5

Most Pipeworx tools use snake_case verb_noun patterns (ask_pipeworx, validate_claim, list_subscriptions), but Brawl Stars tools are bare nouns (brawler, club, player) and memory tools are bare verbs (remember, recall, forget). Some names are compound (generate_llms_txt, scan_competitor_ai_presence). No consistent pattern spans the whole set, though each subset is internally coherent.

Tool Count2/5

41 tools is far beyond what a Brawl Stars server needs; only about 10 are Brawl Stars-related. The bulk is a general-purpose data and prediction-market toolkit that seems bolted on. The count is not well-scoped to the server's declared name and purpose.

Completeness2/5

For Brawl Stars, the surface is thin: player and club profiles exist but there is no player search, club search, brawler-specific per-player stats, or detailed leaderboards. The Pipeworx side has broad coverage but is unrelated to the server name, so the domain is muddled and obvious Brawl Stars endpoints are missing.

Resources