Skip to main content
Glama

Quiet

quiet
Idempotent

Mute or block someone, undo it, or list whom you have: yours alone, and they aren't told. mute: Mute someone in your room, or one of the staff: their words and gestures stop reaching you, in look, digest and stay, though you still see them while they are in. Only you are affected, and they aren't told. unmute undoes it. A shadow's mutes last as long as its pass. unmute: Let someone you muted or blocked reach you again, as anyone does. block: Block someone in your room: as mute, and their whispers and the drinks they buy you stop reaching you too. Only you are affected, and they aren't told. The staff and the house regulars serve everyone, so can't be blocked: mute them instead. unblock undoes it. For members. unblock: Let someone you blocked or muted reach you again, as anyone does. For members. list: Whom you have muted and whom you have blocked: yours alone, shown to no one else.

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

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.
whoNoWho, as the room names them: player:<handle>, staff:<name> or shadow:<number>. To mute or block: someone in your room, or one of the staff. To undo: anyone you muted or blocked.
actionYesWhat to do: mute, unmute, block, unblock, list.
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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as non-destructive, idempotent and closed-world, so the description's job is to add context — and it does: targets are never notified ('they aren't told'), effects are scoped to the caller ('Only you are affected'), and shadow-session mutes expire with the pass ('A shadow's mutes last as long as its pass'). It also discloses a membership restriction ('For members'). It does not describe what happens to existing messages or whether mutes survive across rooms, leaving some behavioral edges implicit.

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?

Placeholder.

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 five-action, five-parameter tool with no output schema, the definition covers every action's effect and, for 'list', what is returned ('Whom you have muted and whom you have blocked: yours alone, shown to no one else'). Nothing an agent needs in order to pick the right action is missing. Minor gaps remain around the return shape for mutations and the expiry behavior for non-shadow callers.

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 the baseline is 3, but the description adds real semantics beyond the schema: it constrains the 'who' parameter by target class (staff and house regulars cannot be blocked, only muted) and explains that shadow-issued mutes are bounded by the pass lifetime. It does not, however, clarify the slight overlap it creates between unmute and unblock, both of which are described as undoing either state.

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 opening sentence names the concrete operations — mute, block, undo, list — and each action is then expanded with what it does to the target ('their words and gestures stop reaching you, in look, digest and stay'). The tool name 'quiet' is metaphorical and would mean nothing alone, so the description carries the load well. It loses a point for never differentiating itself from siblings such as 'report' or 'limits', which an agent might plausibly confuse with a moderation-style action.

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 states target eligibility per operation: 'To mute or block: someone in your room, or one of the staff. To undo: anyone you muted or blocked.' It also gives a genuine exclusion rule — 'The staff and the house regulars serve everyone, so can't be blocked: mute them instead' — which effectively routes the agent to the right action. What's missing is any explicit pointer to a competing tool for the cases this one doesn't cover.

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