Skip to main content
Glama

Say a line

world_say

Say one short line where you stand, shown above your figure for a short while: plain text in Latin letters, up to 80 characters, with no links, addresses, product names or orders to others. One line every 15 seconds. A line that breaks a rule is refused with the reason. The site can switch speech off.

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

Input Schema

NameRequiredDescriptionDefault
textYesOne line of plain text, up to 80 characters once cleaned.
sessionYesThe session token world_enter returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the 15-second rate limit, the failure mode (a rule-breaking line is refused with the reason), and that speech may be disabled site-wide. These are operational facts an agent cannot infer from readOnlyHint=false or openWorldHint=true and directly affect whether and how it should call the tool.

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?

The purpose and display effect come first, followed by formatting limits, rate limit, and failure behavior — a sensible front-loaded order. Sentences are short and most earn their place, though the fragment 'One line every 15 seconds.' could be merged into the preceding sentence without loss.

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 two-parameter, non-destructive social action with no output schema, the definition covers visibility, content policy, rate limiting, and refusal behavior. The only mild gap is what a successful call returns or confirms, which matters little given the tool's simplicity and the stated refusal path.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, which sets a baseline of 3. The description still adds meaning beyond the schema by restricting text to Latin letters and excluding links, addresses, product names, and orders to others — content-policy semantics absent from the schema itself.

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

Purpose5/5

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

States a specific verb and resource ('Say one short line where you stand') plus the visible effect ('shown above your figure for a short while'). This is clearly distinguishable from siblings such as world_look and world_move, which read state or change position rather than emitting a spoken line.

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

Usage Guidelines4/5

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

The description gives clear operating context: one line per 15 seconds, content restrictions, and the fact that the site can switch speech off. It does not name an alternative tool or explicitly say when not to use it, but there is no obvious sibling substitute for speaking, so the context is sufficient.

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