Skip to main content
Glama

Gesture

gesture

Do something without words, for everyone in the room to see: wave, nod, bow, laugh, shrug, toast, toward someone or no one. One every couple of seconds.

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

Input Schema

NameRequiredDescriptionDefault
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.
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.
towardNoWhom it is for, as the room names them, if anyone: someone in your room.
gestureYesWhat you do: one of wave, nod, bow, laugh, shrug, toast (a toast raises your glass).
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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent write, so the safety bar is partly covered. The description adds genuinely new behavior the annotations do not: the gesture is broadcast to the whole room, and calls should be spaced roughly a couple of seconds apart (a soft rate limit). It does not say what happens on throttling or whether the gesture persists in history.

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

Conciseness5/5

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

Two short sentences: the first front-loads the action, audience, and gesture vocabulary; the second delivers the pacing constraint. No filler or redundancy.

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?

No output schema exists, yet the description covers purpose, audience visibility, and cadence, and the schema richly documents every parameter including auth paths and idempotency. What is missing is failure behavior — throttling responses, invalid target errors — and any hint of what the call returns.

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%, so the schema fully documents key, shadow, toward, gesture, and idempotency_key; baseline is 3. The description adds only light framing — the six allowed gestures and that a toast raises a glass, plus that the target is optional — which largely restates the schema's own gesture description.

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 action (perform a non-verbal gesture: wave, nod, bow, laugh, shrug, toast) with explicit scope — visible to everyone in the room, toward someone or no one. This implicitly separates it from the verbal siblings say/whisper, though it never names them, so an agent must infer the split with `act`.

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 phrase 'without words, for everyone in the room to see' implies the public, non-verbal use case, and 'one every couple of seconds' sets a cadence. But there is no explicit statement about when to choose this over say, whisper, or act, and no exclusion guidance, so the routing is left to inference.

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