Skip to main content
Glama
Sealjay

mcp-signal

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_messages

Read-onlyIdempotent

Search Signal message bodies for a keyword across all chats or within one chat. Results return newest-first, including sender, date, chat name, and body text.

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

TableJSON 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

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 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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'read-only with no side effects' largely restates structured data. The description does add ordering (newest-first) and the shape of each result, though the result-field list overlaps with the output schema. Useful but partly redundant.

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 purpose and scope, then usage routing, then return shape. Efficient overall, though the enumerated result fields are somewhat redundant given the output schema is declared.

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?

With full annotations, 100% schema coverage, and an output schema that covers return values, the description's remaining duty is scope, ordering and sibling routing, all of which are present. Nothing needed 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 semantics (substring matching, 1-200 bound, omit-to-search-all) are already documented. The description only restates the one-chat-vs-all-chats scoping that chat_name already encodes, adding no syntax or format detail beyond the schema.

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?

Specific verb (search) plus resource (Signal message bodies), stated scope (one chat or all chats), and result ordering (newest-first). It explicitly distinguishes itself from read_messages, so an agent can route between 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?

States the selection condition ('find messages by content') and names the alternative with its own condition ('read_messages instead to browse a specific chat chronologically'). This is explicit when-to-use and when-not-to-use guidance.

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