Skip to main content
Glama
Sign In
mcp-signal

mcp-signal

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Messages

search_messages
Read-onlyIdempotent

Search Signal message bodies for a keyword across all chats or one chat, returning newest-first results with sender, date, chat name, body, reactions, and attachment metadata.

Instructions

Search Signal message bodies for a keyword, within one chat or across all chats, returned newest-first.

Each result includes sender, date, chat name, body text, reactions, and attachment metadata. Read-only with no side effects. Use this to find messages by content. Use read_messages instead to browse a specific chat chronologically.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching messages to return, between 1 and 200. Defaults to 20.
queryYesCase-insensitive substring to search for within message bodies.
chat_nameNoExact chat name to restrict the search to a single chat. Omit to search across all chats.

Output 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 matching messages to return, between 1 and 200."New value: +"Maximum number of matching messages to return, between 1 and 200. Defaults to 20."
  2. Changed3 schema fields changedv0.1.3
    • addedInput schema / properties / chat_name / description
      Added value: +"Exact chat name to restrict the search to a single chat. Omit to search across all chats."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching messages to return, between 1 and 200."
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive substring to search for within message bodies."
  3. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive, so the 'Read-only with no side effects' sentence adds nothing new. However the description does add genuinely non-annotated behavior: newest-first ordering, the per-chat vs. global scope, and the exact result fields (sender, date, chat name, body, reactions, attachment metadata). Pagination behavior is still unstated, keeping it below 5.

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?

Front-loaded with the core action and scope, then results, then routing. Nearly every sentence earns its place, though 'Read-only with no side effects' duplicates the annotations and could be dropped.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them usefully. Scope, ordering, and sibling routing are all present; nothing an agent needs to invoke the tool correctly is missing.

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 query, limit, and chat_name are fully documented in the schema, including case-insensitivity and the 1-200 range. The description only restates the chat-vs-all scope and adds no format or syntax detail beyond the schema; baseline 3 applies.

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 ('Search Signal message bodies'), the searchable scope (one chat or all chats), and the ordering (newest-first). It explicitly contrasts itself with read_messages, so an agent can distinguish the two 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 explicit selection criteria: 'Use this to find messages by content. Use read_messages instead to browse a specific chat chronologically.' The alternative and the condition that selects it are both named.

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