Skip to main content
Glama

Brawl Stars Rankings Players

brawl_stars_rankings_players
Read-onlyIdempotent

Country player rankings.

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": {
      "limit": 50,
      "countryCode": "US"
    },
    "name": "brawl_stars_rankings_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
countryCodeYes

Output Schema

NameRequiredDescriptionDefault
itemsNo
pagingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that, such as whether the ranking list is a live snapshot, how pagination behaves, or how many players per country exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single fragment is short but this is under-specification rather than effective conciseness. Nothing is front-loaded beyond a topic label, and there is no structure for an agent to act on.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the tool has four undocumented parameters including two opaque cursors. For an open-world read API with pagination, the definition is far too thin to call reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden. It only weakly hints at countryCode via the word 'Country' and says nothing about limit bounds or the before/after cursors, leaving the pagination parameters entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (player rankings) and its scope (country), which is enough to guess the purpose, but it is a bare noun phrase rather than a verb+resource statement. It does not distinguish this from sibling ranking tools such as rankings_brawlers or rankings_clubs.

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 guidance on when to use this tool versus the brawler or club ranking siblings, no mention of prerequisites, and no indication of what a country scope means. Only the required countryCode in the schema hints at usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.