Skip to main content
Glama

Chessar.io

join

Join a world with your army.

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": {
      "world": "<world>"
    },
    "name": "join"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
worldYesWorld id, see the worlds tool (e.g. 10s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden and largely drops it. It implies a state-changing action tied to an army but says nothing about irreversibility, cooldowns, what happens to the army on joining, or whether the player must leave a current world first.

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?

A single short sentence with no filler, so nothing is wasted. But the brevity here reflects under-specification rather than efficient front-loading—there is no structure or detail to organize.

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 mutation-style game action with no annotations, no output schema, and an undocumented name parameter, the description is far too thin. An agent would not know what state this changes or how to pick the name argument from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the world enum is already documented in the schema, and the description does not add to it. The name parameter is undocumented in both schema and description, so the description provides no compensating meaning for the coverage gap.

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?

"Join a world with your army" names a specific verb and resource, so the general action is identifiable and distinguishable from siblings like worlds or move. However it never says what joining actually means in game terms (start a match, register the army, enter a queue), so the purpose is only sketched.

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 or when-not-to-use guidance at all. The description does not mention prerequisites (e.g., needing an existing army or a valid world from the worlds tool) or any alternative tool to use instead.

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.

Resources