Skip to main content
Glama

tanks_by_slug_ratings

Tank community rating

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>",
      "slug": "<slug>"
    },
    "name": "tanks_by_slug_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTank slug (e.g. is-7).
regionYesGame server region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/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 behavioral burden, and it discloses nothing: not what a 'community rating' is (score, scale, sample size), how it is aggregated, or whether region affects the result. The tool is effectively opaque.

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?

Three words is not bloat, but this is under-specification rather than conciseness — nothing meaningful is front-loaded because nothing is said. The single phrase does not earn its place as a definition.

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?

With no output schema and no annotations, the description is the only source of behavioral context, and it supplies none. Parameters are covered by the schema, but an agent cannot know the rating's meaning, scale, or return shape before invoking.

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 100% with both parameters documented (slug example 'is-7', region enum eu/na/asia), so the baseline is 3. The description adds no meaning beyond the schema, but the schema itself is complete.

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 phrase 'Tank community rating' is essentially a restatement of the tool name, with 'community' being the only added signal. It weakly distinguishes this from the sibling tanks_by_slug_ratings_me (personal ratings), but provides no verb or scope statement. Purpose is inferable but vague.

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 call this versus tanks_by_slug_ratings_me, tanks_ratings, or tanks_by_slug. No prerequisites or context are given. The agent must infer usage purely 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.