Skip to main content
Glama

game_send_message

[STATE] Send a chat message to your anonymous opponent during the game. Keep messages casual and human-like. Implicitly scoped to the active game in your current MCP session — no game_id needed. Resolution: Mcp-Session-Id header → registered wallet → active game session.

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": {
      "text": "<text>"
    },
    "name": "game_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe chat message text to send.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered structurally. The description goes beyond that by disclosing the implicit resolution chain (Mcp-Session-Id header → registered wallet → active game session), which tells the agent how the target is chosen without an ID — genuinely useful behavioral context. It omits failure behavior when no active game exists and any rate/delivery constraints, keeping it short of a 5.

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?

Content is front-loaded with the action, followed by scoping and resolution details in a terse arrow notation. The stray "[STATE]" marker and the stylistic "casual and human-like" sentence are minor padding, but nothing is genuinely redundant.

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

Completeness4/5

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

For a one-parameter, no-output-schema tool, the definition covers target resolution and the implicit-session scoping that an agent would otherwise get wrong. Missing only edge-case behavior (no active match, message rejection), which is a modest gap rather than a blocker.

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?

With a single parameter at 100% schema description coverage, the schema already documents "text" fully. The description adds only the scoping insight ("no game_id needed"), which clarifies that the absent parameter is intentional rather than an oversight, but contributes no format or content constraints beyond 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?

The description states a specific verb and resource — "Send a chat message to your anonymous opponent" — which cleanly separates it from the read-side sibling game_get_messages. It doesn't name an alternative outright, and the leading "[STATE]" token is unexplained noise, but the core purpose is unambiguous.

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?

Usage context is implied by "during the game" and by the explicit note that it's scoped to the active game in the current MCP session, plus the caution to keep messages casual and human-like. There is no explicit when-to-use versus when-not framing (e.g., relative to game_get_messages or what to do if no game is active), so guidance is present but incomplete.

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