Skip to main content
Glama

search_messages

Read-onlyIdempotent

Search all Mizito chats at once for matching messages, returning up to 15 results per page with the source chat and offset-based pagination.

Instructions

Search all chats at once (Mizito's global message search). Returns up to 15 hits per page with the chat each came from; page with offset/next_offset.

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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's job is to add operational detail — which it does: a 15-hit page cap, inclusion of the originating chat per hit, and offset/next_offset pagination. It still doesn't say how hits are ordered or whether results span workspaces, but the added context is substantive for a read tool.

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?

Three compact clauses, front-loaded with scope, then result shape, then pagination. No repetition of the name and no filler.

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 two-parameter read tool with an output schema already documenting returns, the description covers the essentials: scope, page size, hit payload, and paging mechanics. The remaining gap is query matching semantics, which matters for a free-text search but is a modest omission given the tool's simplicity.

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 coverage is 0%, so the description must carry the parameters. It clarifies offset implicitly through 'page with offset/next_offset', but leaves 'query' entirely uncharacterized — no indication of what fields are matched (message body, sender, chat name) or whether syntax like quoting or operators is supported.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search all chats at once', 'global message search') and scopes it clearly as cross-chat rather than single-chat, which implicitly contrasts with search_chat. It stops short of naming the sibling, so the differentiation is inferable rather than explicit.

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

Usage Guidelines3/5

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

The phrase 'all chats at once' implies when to reach for this over a per-chat search, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the routing rule from the word 'global'.

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