Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_typing

Idempotent

Show or cancel the 'typing…' indicator in a Signal DM or group before sending an automated reply. Use stop=true to cancel early; expires after ~15s.

Instructions

Show or cancel the 'typing…' indicator in a DM or group. Purely cosmetic; use before send_message / send_group_message in an automated reply. recipient: E.164 number for a DM; group_id for a group (from list_groups); at least one is required. stop=true cancels an active indicator early (default false = start). The indicator expires by itself after ~15 seconds and is cleared when you send, so stop is rarely needed; one call per message is enough — don't loop. If the recipient disabled typing indicators it is silently ignored. Contacts Signal's servers; nothing is stored. Returns {status: 'typing indicator sent'}.

Input Schema

NameRequiredDescriptionDefault
stopNoSet to true to cancel an active typing indicator (default: false = start typing)
group_idNoGroup ID (base64) to show typing in a group
recipientNoPhone number in E.164 format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.40.1
    • addedInput schema / properties / group_id
      Added value: +{
+  "description": "Group ID (base64) to show typing in a group",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "recipient"
-]
  2. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / stop / description
      Previous value: -"True to stop typing indicator (default: False)"New value: +"Set to true to cancel an active typing indicator (default: false = start typing)"
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare the safety profile (non-destructive, idempotent, open-world), and the description layers on non-obvious behavior: the indicator auto-expires in ~15s, is cleared on send, is silently ignored when the recipient has disabled indicators, contacts Signal's servers, and stores nothing. It even states the return value without an output schema.

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?

Front-loaded with the core purpose, then parameter semantics, then behavioral caveats and the return shape. Dense but every sentence carries operational information; nothing is redundant padding.

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

Completeness5/5

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

For a small cosmetic tool with no output schema, the description covers purpose, parameter interpretation, lifecycle, edge cases, and the literal return payload. Nothing an agent needs to call it correctly is missing.

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 meaning the schema lacks: it clarifies that recipient and group_id are alternatives ('at least one is required') even though the schema marks zero required params, and that group_id comes from list_groups. The '~15 second' expiry and silent-ignore behavior also disambiguate stop's value.

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 ('show or cancel') plus the resource ('typing… indicator') and its scope (DM or group), which no sibling tool covers. An agent can distinguish it immediately from send_message/send_group_message without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ('use before send_message / send_group_message in an automated reply'), an explicit when-not ('stop is rarely needed', 'one call per message is enough — don't loop'), and points to sibling tools by name. Routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools