local-mcp

Search Messages

search_messages

Read-only

Searches iMessage conversations by content, sender name, or date range.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 30)
`query`	No	Text to search for in message content (optional if from_sender is set)
`since`	No	ISO8601 date — only return messages on or after this date (optional, e.g. '2026-04-10' or '2026-04-10T00:00:00Z')
`until`	No	ISO8601 date — only return messages on or before this date (optional). Combine with 'since' to search a date range with no text query.
`from_sender`	No	Substring of sender name/handle to filter by (optional)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`query`	No
`since`	No
`until`	No
`results`	No
`from_sender`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 22, 2026

addedInput schema / properties / until

Added value: +{
+  "description": "ISO8601 date — only return messages on or before this date (optional). Combine with 'since' to search a date range with no text query.",
+  "type": "string"
+}

addedOutput schema / properties / until
```
Added value: +{
+  "type": "string"
+}
```

First observedJun 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already mark this as read-only/non-destructive. The description adds the search criteria context (content/sender/date range) but no additional behavioral traits like sorting or pagination. No contradiction.

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?

Single sentence, 13 words, front-loaded with 'Searches iMessage conversations'. No redundancy.

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 read-only search tool with a full output schema and complete parameter descriptions, the concise description suffices. It could mention that query is optional and date-only searches are possible, but the schema already handles this.

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?

Input schema descriptions cover all 5 parameters (100%). The description provides a high-level summary but does not add details beyond the schema, so 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?

The description uses a specific verb ('Searches') and resource ('iMessage conversations'), and enumerates three distinct search facets (content, sender name, date range). This clearly differentiates from sibling messaging search tools by naming iMessage explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like read_messages or signal_search_messages. The description states the function but not the decision context or exclusions.

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

All local-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.