Skip to main content
Glama

search

Search full-text across WhatsApp messages, image OCR, voice notes, and PDFs using FTS5 syntax. Use it to find any mention of a topic, phrase, or prefix across all chat history.

Instructions

Full-text search across ALL surfaces — typed messages, image OCR and descriptions, voice-note transcripts, document filenames and PDF body text. FTS5 syntax: "exact phrase", AND, OR, NOT, NEAR/3, prefix*. Use this first for any 'did anyone mention X' question; fall back to query for joins and aggregates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomaximum hits, default 25, max 100
queryYesFTS5 match expression, e.g. 'kitchen AND budget', '"exact phrase"', 'pizz*'

Output Schema

NameRequiredDescriptionDefault
hitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.24

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden. It discloses the important behavioral trait that indexing spans OCR, transcripts and PDF bodies — non-obvious and material to whether the agent trusts the result. It does not discuss ranking, result ordering, permissions, or what an empty result implies, so it stops short of full behavioral disclosure.

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?

Two sentences, no filler. Scope is front-loaded before syntax, and syntax before routing advice, which is the correct order for an agent deciding whether to call at all before crafting the query string.

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?

An output schema exists, so return values need not be described, and both parameters are fully documented in the schema. What remains uncovered is minor but real: no indication of result ranking, whether results are paginated beyond 'limit', or behavior on malformed FTS5 syntax. For a two-parameter read tool this is close to complete.

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?

Schema coverage is 100%, so the baseline is 3; the description earns the bump by adding FTS5 operators the schema description does not enumerate (NOT, NEAR/3, prefix*) and by clarifying that the match expression applies across all indexed surfaces. The 'limit' parameter is left entirely to the schema, which is acceptable given full schema documentation.

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 (full-text search) and resource (all surfaces) and then enumerates exactly what is indexed: typed messages, image OCR, voice-note transcripts, document filenames and PDF body text. An agent immediately understands both the action and the unexpected breadth of coverage, distinguishing it from the sibling 'query' tool.

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 an explicit positive trigger ("Use this first for any 'did anyone mention X' question") and an explicit alternative with conditions for switching ("fall back to query for joins and aggregates"). This is textbook routing guidance with both a default and a fallback.

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