Skip to main content
Glama

tanks_by_slug_history

Tank changes history

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

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.3/5.0
Behavior2/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 almost nothing. It weakly implies a read-only historical view but says nothing about pagination, time window, whether changes are patch notes or balance edits, or response shape.

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

Conciseness3/5

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

Three words with no filler, so nothing is wasted, but this brevity reflects under-specification rather than disciplined concision. There is no structure to speak of and nothing is front-loaded beyond the resource name.

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 annotations and no output schema, the description is the only source of behavioral context, and it supplies none. An agent would not know what a "change" is, whether results are time-ordered, or how much history is returned.

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%: the slug format (e.g. is-7) and the region enum are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

"Tank changes history" is essentially a restatement of the tool name (tanks_by_slug_history) with no verb and no scope. It does not distinguish this from the sibling tanks_changes, which plausibly returns the same conceptual data, so an agent cannot route between them from the description alone.

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 statement of when to use this tool versus tanks_changes, tanks_by_slug_detail, or maps_by_slug_history. The only implicit guidance is that it operates per-tank via the slug selector encoded in 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.