Skip to main content
Glama
Sign In

Brawl Stars

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Brawlers

brawlers
Read-onlyIdempotent

Brawl Stars official API — complete list of all brawlers with their numeric ID, name, star powers, and gadgets.

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": {},
    "name": "brawlers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsNo
pagingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Brawler ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Brawler name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "paging": {
+      "properties": {
+        "cursors": {
+          "properties": {
+            "after": {
+              "description": "Cursor for next page",
+              "type": "string"
+            },
+            "before": {
+              "description": "Cursor for previous page",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and side-effect expectations. The description adds context about the data source ('official API') and the data structure (list with ID, name, star powers, gadgets), which helps set expectations about the response content. This goes beyond the annotations without contradicting them.

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, compact sentence that front-loads the key information: it is the official Brawl Stars API and returns a complete list of brawlers with specific attributes. No filler or redundant phrasing; every word contributes to understanding the tool's purpose and output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, a rich set of annotations, and an output schema, the description fully covers what the tool does and what it returns. The description explains the return fields explicitly, which complements the output schema. For a simple list endpoint, this is complete; no additional behavioral notes are necessary.

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 tool has zero parameters, so there is nothing to document. The schema coverage is 100% (empty schema). The description correctly focuses on the return payload rather than parameters, which is appropriate for a no-argument tool. Baseline for 0 params is 4.

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 the tool provides a complete list of all brawlers with specific fields (numeric ID, name, star powers, gadgets). This is a specific resource (brawlers) with a clear scope (all, complete list), distinguishing it from the sibling tool 'brawler' which likely targets a 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 Guidelines3/5

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

The description implies the tool is for retrieving the full roster of brawlers, which is a clear use case. However, it does not explicitly contrast with alternatives like 'brawler' or 'rankings_brawlers', nor does it mention when not to use this tool. Usage context is implied rather than explicitly 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 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