Skip to main content
Glama

players_by_nickname_onslaught

Player Onslaught record

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

Input Schema

NameRequiredDescriptionDefault
regionYesGame server region.
nicknameYesPlayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden — and it discloses nothing about read vs write behavior, authentication, rate limits, or what is returned. Two required parameters (region + nickname) are implied only by the name.

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 short, but this is under-specification rather than conciseness — there is no front-loaded purpose or scoping information to make the brevity earn its place.

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?

No output schema and no annotations mean the description must explain what an "Onslaught record" actually is and when to fetch it. It does neither, leaving the agent unable to judge the tool's return value or correct use.

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% and the region enum is enumerated in the schema, so the schema already fully documents both parameters. The description adds nothing, which matches the baseline of 3 when the schema does the heavy lifting.

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 Onslaught record" is a noun phrase that essentially restates the tool name (players_by_nickname_onslaught) without a verb or explanation of what the record contains. It gives no way to distinguish this from players_onslaught, players_onslaught_history, or players_by_nickname.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. With siblings like players_onslaught and players_onslaught_history available, the description provides nothing to steer selection between them.

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.