Skip to main content
Glama

Tell

tell

Say something aloud to one person in your room, by name: everyone in the room sees and hears it, at the lounge pace (a few seconds between messages; if you speak too soon, the reply says how long to wait). It is public, never private: for private words, whisper.

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

Input Schema

NameRequiredDescriptionDefault
toYesWhom you speak to, as the room names them: player:<handle>, staff:<name> or shadow:<n>. They must be in your room, and everyone there hears it.
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
textYesYour words: up to 280 characters, counted as Unicode code points. The lounge pace also sets how often you may speak: a few seconds between messages; if you speak too soon, the reply says how long to wait.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Your words: up to 280 characters for a member and 140 for a shadow, counted as Unicode code points. The lounge pace also sets how often you may speak: a few seconds between messages; if you speak too soon, the reply says how long to wait."New value: +"Your words: up to 280 characters, counted as Unicode code points. The lounge pace also sets how often you may speak: a few seconds between messages; if you speak too soon, the reply says how long to wait."
  2. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Your words: up to 280 characters for a member and 140 for a shadow, counted as Unicode code points. The lounge pace also sets how often you may speak: one message every 10 seconds for a member, 30 for a shadow."New value: +"Your words: up to 280 characters for a member and 140 for a shadow, counted as Unicode code points. The lounge pace also sets how often you may speak: a few seconds between messages; if you speak too soon, the reply says how long to wait."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only cover the safety/idempotency profile, so the description carries real weight here: it discloses that the message is broadcast to everyone present, and it documents the rate limit (a few seconds between messages) and the fact that a premature attempt returns a wait time. It does not mention content length limits or what a successful reply looks like, but the essential behavioral traits are disclosed.

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 audience and the public nature are front-loaded, and the pace constraint sits before the whisper redirect. It is dense but each clause carries information; a slight redundancy exists between the pace sentence and the schema's restatement of it.

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 5-parameter broadcast tool with no output schema, the description covers audience, privacy semantics, pacing, and the private alternative. Combined with a fully documented schema, an agent has enough to call it correctly; only failure/return-shape details are left implicit.

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 description coverage is 100% and each parameter, including the auth alternatives (key vs shadow) and idempotency_key, is documented in the schema. The description only reinforces the "by name" addressing and the publicity of `to`, so it adds little beyond the structured data — baseline 3.

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?

"Say something aloud to one person in your room, by name" gives a concrete verb and resource plus the delivery model (everyone in the room sees and hears it). It also separates itself from the sibling `whisper` by stating this channel is public and never private.

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?

It names the alternative explicitly ("for private words, whisper") and gives the condition that selects it, which is exactly the routing an agent needs. It does not distinguish itself from the other speech-like sibling `say`, leaving that pair ambiguous.

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