Skip to main content
Glama
Sealjay

mcp-signal

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_groups

Read-onlyIdempotent

Fetch Signal groups with group_id, name, description, members, and admins, sorted alphabetically; filter by name to get group IDs needed for sending messages.

Instructions

List Signal groups with group_id, name, description, members, and admin lists, sorted alphabetically.

Read-only with no side effects. Queries signal-cli when available; falls back to the local desktop database (without group_id). Use this to obtain group_id values needed by send_message. Use list_chats instead for a combined view of both direct and group chats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of groups to return, between 1 and 200. Defaults to 50.
queryNoCase-insensitive substring to filter group names. Empty string returns all groups.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of groups to return, between 1 and 200."New value: +"Maximum number of groups to return, between 1 and 200. Defaults to 50."
  2. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of groups to return, between 1 and 200."
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive substring to filter group names. Empty string returns all groups."
  3. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description correctly adds value beyond them by disclosing the data source: signal-cli when available, with a fallback to the local desktop database that omits group_id. That degradation caveat is real behavioral context an agent must know. It stops short of detailing result shape, but an output schema exists to carry that.

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?

The core verb and resource lead, followed by behavior, then routing. Every sentence carries a distinct load – fields, safety, data source, and two sibling disambiguations – with no 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 filtered, read-only list tool this is complete: it covers purpose, safety, data-source fallback behavior, pagination-adjacent filtering via schema, and routing to the correct sibling. The existence of an output schema means return values need not be explained here.

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 both limit and query are fully documented in the schema already. The description adds no syntax or format detail for either parameter, making the baseline 3 appropriate.

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 ("List Signal groups") and enumerates the returned fields (group_id, name, description, members, admin lists) plus sort order. It explicitly distinguishes itself from the sibling list_chats, so an agent can tell the two apart without opening either 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 two explicit routing rules: use this to obtain group_id values needed by send_message, and use list_chats instead for a combined direct+group view. Both the when-to-use and the alternative are named, leaving nothing to inference.

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