Skip to main content
Glama

players_by_nickname_clan

Player current clan

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

Input Schema

NameRequiredDescriptionDefault
regionYesGame server region.
nicknameYesPlayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/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 the return shape, not whether historical clans are included (a sibling, clans_by_tag_previous_clans, suggests this distinction matters), not auth or rate-limit behavior. Three words convey zero behavioral context for a two-parameter query.

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?

The description is only three words with no padding, so there is nothing wasteful to trim. However, it is under-specified rather than genuinely concise, so it earns no credit for efficiency.

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?

For a two-param player lookup with no output schema, the description should at least clarify what 'current clan' means (name only? tag? full clan summary?) and how it differs from clan-history siblings. That ambiguity is left entirely unresolved.

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 (with an enum of eu/na/asia) and nickname are both 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?

The description 'Player current clan' is a noun fragment that essentially restates the tool name (players_by_nickname_clan) rather than stating a verb and resource. It hints at the subject matter but does not say what the tool actually does (fetch? summarize? compare?).

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, no prerequisites, and no mention of alternatives such as clans_by_tag or players_by_nickname. An agent must infer entirely from the name which of the many player/clan siblings applies.

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.