Skip to main content
Glama

Chessar.io

state

Full world snapshot (1 per second).

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": "state"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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 it does disclose one genuinely useful trait: the call is throttled to one per second, which an agent should know before polling. It says nothing about permissions, payload size, whether the snapshot is read-only and side-effect free, or how stale the data is. That is a partial but real disclosure.

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

Conciseness4/5

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

One front-loaded sentence with no filler, and the rate constraint is placed where it will be read. It is arguably over-compressed, since 'Full world snapshot' leaves the payload undefined, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one enum parameter, no nesting, no output schema), so the burden is modest, and the description plus schema is enough to invoke it correctly. It is not complete enough to tell an agent what a snapshot actually contains or why it differs from status or view, which matters for choosing between them.

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 coverage is 100% and the single world parameter has an enum plus a pointer to the worlds tool, so the schema does the heavy lifting. The description's word 'world' mirrors the parameter but adds no format or selection guidance. Baseline 3 applies when the schema is fully documented.

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?

The description identifies the resource (a full snapshot of a world) and even embeds a rate note, so an agent knows roughly what it returns. But it supplies no verb and no differentiation from nearby siblings such as worlds, status, or view, which all sound like they read world-related information. Purpose is inferable rather than stated.

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 guidance on when this tool should be used instead of alternatives like status, view, or worlds, and no stated prerequisites. The '1 per second' note is a limit, not a usage rule. The agent must guess the scenario from the six-word description.

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