Skip to main content
Glama

Brawl Stars

by io.github.pipeworx-io

Club

club
Read-onlyIdempotent

Brawl Stars official API — full club profile for a club tag: name, description, type, trophies required, total trophies, and member count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoClub tag
nameNoClub name
typeNoClub type
badgeIdNoClub badge ID
membersNo
trophiesNoClub total trophies
descriptionNoClub description
requiredTrophiesNoRequired trophies to join

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": "#2CCCCCCCC"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "badgeId": {
+      "description": "Club badge ID",
+      "type": "number"
+    },
+    "description": {
+      "description": "Club description",
+      "type": "string"
+    },
+    "members": {
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Member name",
+            "type": "string"
+          },
+          "role": {
+            "description": "Member role",
+            "type": "string"
+          },
+          "tag": {
+            "description": "Member tag",
+            "type": "string"
+          },
+          "trophies": {
+            "description": "Member trophies",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Club name",
+      "type": "string"
+    },
+    "requiredTrophies": {
+      "description": "Required trophies to join",
+      "type": "number"
+    },
+    "tag": {
+      "description": "Club tag",
+      "type": "string"
+    },
+    "trophies": {
+      "description": "Club total trophies",
+      "type": "number"
+    },
+    "type": {
+      "description": "Club type",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the safety profile. The description adds the list of returned fields, which is useful context, but no details on rate limits, authentication, or edge cases. No contradiction with annotations.

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, focused sentence that directly states the purpose and key return fields. Every word earns its place, with no filler or redundancy.

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?

Given the tool's simplicity (one parameter), the presence of annotations, and an output schema, the description is adequate. It would be more complete with explicit usage guidance or alternative tool references, but the current level of detail is sufficient for a basic profile lookup.

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?

The schema has only 'tag' with no description, so coverage is 0%. The description clarifies that the tag is a club tag, and the example '#2CCCCCCCC' provides format guidance. This compensates partially, but the description does not fully specify valid tag formats or special characters.

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 the tool returns a 'full club profile' for a club tag and lists specific fields, clearly indicating the resource and scope. It lacks an explicit verb but is still understandable. It differentiates from sibling tools like 'club_members' by focusing on the overall profile rather than a membership list.

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?

No guidance is given on when to use this tool versus alternatives such as 'club_members' or 'rankings_clubs'. The description implies its use for fetching club details, but it does not state exclusions or reference sibling tools.

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