Skip to main content
Glama

players_by_nickname_battles

Player battles

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>",
      "nickname": "<nickname>"
    },
    "name": "players_by_nickname_battles"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapNoOnly battles on this arena, by the game's own map id (`05_prohorovka`). `facets.maps` lists the ones it has.
modeNoOnly battles of this mode, by the game's own `bonusType` (1 is random battles). `facets.modes` lists the ones this account has.
pageNoWhich page of `limit` battles, newest first, counted from one. The first by default; `total` in the answer says how many there are.
tankNoOnly battles this account fought in this vehicle, by its tank id. `facets.tanks` lists the ones it has.
limitNoBattles per page, newest first. Ten by default, a hundred at most.
facetsNo`true` to also answer `facets`: every mode, vehicle, map and result this account's battles have, counted over all of them regardless of the filters above. Left out by default, since only a page that draws filters needs it.
regionYesGame server region.
resultNoOnly battles this account won, lost or drew.
languageNo
nicknameYesPlayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / facets
      Added value: +{
      +  "description": "`true` to also answer `facets`: every mode, vehicle, map and result this account's battles have, counted over all of them regardless of the filters above. Left out by default, since only a page that draws filters needs it.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Battles to return, newest first. Ten by default."New value: +"Battles per page, newest first. Ten by default, a hundred at most."
    • addedInput schema / properties / map
      Added value: +{
      +  "description": "Only battles on this arena, by the game's own map id (`05_prohorovka`). `facets.maps` lists the ones it has.",
      +  "type": "string"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "Only battles of this mode, by the game's own `bonusType` (1 is random battles). `facets.modes` lists the ones this account has.",
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of `limit` battles, newest first, counted from one. The first by default; `total` in the answer says how many there are.",
      +  "type": "string"
      +}
    • addedInput schema / properties / result
      Added value: +{
      +  "description": "Only battles this account won, lost or drew.",
      +  "enum": [
      +    "win",
      +    "loss",
      +    "draw"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tank
      Added value: +{
      +  "description": "Only battles this account fought in this vehicle, by its tank id. `facets.tanks` lists the ones it has.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

C2/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it states nothing beyond "Player battles." It omits that this is a read operation, default newest-first pagination, limit caps, and the special facets behavior documented only in the schema.

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 two-word description is technically concise but is under-specified rather than efficient. It is not front-loaded with useful scope, differentiation, or behavioral context.

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?

For a 10-parameter tool with no annotations or output schema and many sibling players_* and battles_* tools, the description is far too thin to support correct tool selection. The rich input schema mitigates parameter explanation, but not purpose, usage, or scope.

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?

Schema description coverage is 90%, so the schema already explains the ten parameters in detail, including filters, pagination, enums, and facets. The description adds no parameter meaning, but the high schema coverage sets the baseline at 3.

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

Purpose2/5

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

The description is just "Player battles," which essentially restates the tool name and resource without a specific verb or scope. It does not clarify that it lists a given nickname's battles in a region, nor does it distinguish this from siblings such as players_by_nickname_sessions or battles_by_id.

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 alternatives, no mention of the required region and nickname, and no exclusions or prerequisites. The agent must infer usage entirely from the name and schema.

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.