Skip to main content
Glama

search_messages

Search iMessages by keyword to find past conversations without scrolling through your entire message history.

Instructions

Search iMessages by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:38-38 (registration)
    Tool 'search_messages' is registered in the TOOLS array as ['search_messages', 'Search iMessages by keyword']
    ["search_messages", "Search iMessages by keyword"],
  • Generic stub handler for all tools including 'search_messages' that returns an inspection placeholder message
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
  • Empty schema object '{}' passed as parameter schema for all tools including 'search_messages'
    server.tool(name, desc, {}, async () => ({
  • server.js:106-110 (registration)
    Tools are registered in a loop iterating over the TOOLS array, calling server.tool() for each entry
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior3/5

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

No annotations provided. Description implies a read operation but doesn't specify return format, pagination, or ordering. Adequate for a simple search, but lacks explicit behavioral details.

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?

One sentence, no wasted words. Front-loaded with verb and resource.

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?

Simple tool with no parameters and no output schema. Description adequately covers purpose. Could mention that results are returned as a list of messages.

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?

Input schema has zero parameters, so description needs no parameter info. Baseline 4 for 0 params.

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?

Description clearly states verb 'Search', resource 'iMessages', and scope 'by keyword'. Distinguishes from siblings like search_emails and read_messages.

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 (e.g., read_messages, search_emails). Agent must infer from tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server