Skip to main content
Glama

Brawl Stars

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Brawler

brawler
Read-onlyIdempotent

Brawl Stars official API — detail for a single brawler by numeric ID: name, star powers with descriptions, and gadgets with descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBrawler ID
nameNoBrawler name
gadgetsNo
starPowersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 16000000
+  },
+  {
+    "id": 16000001
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "gadgets": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Gadget ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Gadget name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Brawler ID",
+      "type": "number"
+    },
+    "name": {
+      "description": "Brawler name",
+      "type": "string"
+    },
+    "starPowers": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Star power ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Star power name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "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 cover read-only, idempotent, and non-destructive behavior. The description adds context about the response content (name, star powers, gadgets) and source ('official API'), which goes beyond the annotations. No unknown side effects or caveats are mentioned, but this is acceptable given the annotation coverage.

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, tightly worded sentence that conveys the tool's purpose and output. It includes no filler and is front-loaded with the API context.

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?

For a simple single-entity lookup with an output schema available, the description is adequately complete. It covers the essential function and return values. It does not differentiate from sibling tools, but this is a minor gap given the tool's simplicity.

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 a single required 'id' of type number. The description adds that it is a 'numeric ID' for a brawler, which gives minimal semantic meaning beyond the schema. It does not explain the ID's range, origin, or how to obtain it, so the compensation for low schema coverage is limited.

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 states it provides detailed information for a single Brawl Stars brawler by numeric ID, listing specific return fields (name, star powers, gadgets). This differentiates it from the sibling 'brawlers' tool by emphasizing 'single brawler'.

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?

The description implies usage for looking up a specific brawler's details, distinguishing it from the plural 'brawlers' tool by the singular/plural distinction. However, it does not explicitly state when not to use the tool or name alternatives.

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
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.

Resources