Skip to main content
Glama

players_onslaught_history

Onslaught season 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>"
    },
    "name": "players_onslaught_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesGame server region.
seasonNoSeason event id to load (default the current season). From the seasons list on the leaderboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. "History" weakly implies a read-only retrospective query, but there is no mention of pagination, time coverage, default season behavior, or return shape.

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 conciseness but under-specification; there is no wasted text because there is almost no text. It is front-loaded only trivially, and the agent gains nothing actionable.

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?

No annotations and no output schema, so the description should explain the result set and how seasons are identified, but it does neither. The unresolved tension between the players_-prefixed name and a region-only signature is left entirely unexplained.

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%: region's enum and meaning plus the season default are fully documented in the schema, including the pointer to the seasons list on the leaderboard. 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?

"Onslaught season history" restates the tool name without a verb or object; it never says whose history is returned or what a record contains. This is especially problematic given the name carries a "players_" prefix while the only required parameter is a server region, leaving the agent unsure whether this is global or player-scoped data.

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?

No when-to-use guidance is offered. The description does not distinguish this tool from close siblings such as players_onslaught or players_by_nickname_onslaught, so the agent must guess which onslaught endpoint to call.

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.