Skip to main content
Glama

Chessar.io

say

Send a nearby or direct chat message.

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>",
      "channel": "<channel>",
      "text": "<text>"
    },
    "name": "say"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 full disclosure burden and largely fails it. "Nearby" hints that the message is broadcast to nearby players rather than one recipient, which is useful, but there is nothing about who the sender is, delivery preconditions, rate limits, or failure behavior when a target is unreachable.

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?

A single front-loaded sentence with zero filler or repetition. Its brevity is efficient, though the terseness shades into under-specification rather than true economy.

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 4-parameter mutation tool with no annotations, no output schema, and 75% of parameters undocumented in the schema, the description leaves too much unresolved. An agent cannot determine how to address the `to` field or what preconditions apply before sending.

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 only 25%: only `world` is documented, while `to`, `text`, and `channel` have no descriptions. The phrase "nearby or direct" loosely maps to the channel enum, but the critical `to` parameter (recipient identity format) is entirely unexplained and the 400-character limit is only implicit in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Send") and resource ("chat message") plus a scope qualifier ("nearby or direct") that maps onto the channel enum, so it is distinguishable from read-oriented siblings like messages. It stops short of naming any sibling explicitly, so it earns a 4 rather than a 5.

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

Usage Guidelines3/5

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

The purpose implies when to use it, and "nearby or direct" hints at the two delivery modes, but there is no explicit when-to-use vs. alternative guidance and no mention of related actions such as reading messages or joining a world first. Usage is inferred rather than stated.

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