Skip to main content
Glama

players_by_nickname_tanks

Player tanks

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_tanks"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
regionYesGame server region.
nicknameYesPlayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: no read-only nature, no rate limits, no auth requirements, no pagination or return shape. This is a two-word fragment that leaves all behavioral traits unknown.

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?

It is certainly short, but this is under-specification rather than conciseness: two words with no actionable content, so no sentence earns its place because there is effectively only a label.

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

Completeness1/5

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

For a 3-parameter, 2-required tool with no annotations, no output schema, and an undocumented parameter, the description is completely inadequate. Nothing an agent needs to invoke it correctly is present.

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 coverage is only 67%, and the undocumented 'mode' parameter gets no explanation in either the schema or the description. The description adds no meaning for region, nickname, or mode beyond what the schema already states.

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?

"Player tanks" essentially restates the tool name and gives no verb or outcome: it doesn't say whether it lists tanks owned, played, or mastered by the player. It also fails to distinguish itself from the near-identical sibling players_by_nickname_tanks_by_slug.

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 indication of when to use this tool versus players_by_nickname_tanks_by_slug, players_by_nickname_battles, or tanks_by_slug. The agent must infer usage entirely from the name.

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.