Skip to main content
Glama

search_chat

Read-onlyIdempotent

Search messages within a specific chat by ID or title, filtering by text query or sender and returning newest matches first with paging.

Instructions

Search inside one chat (id or title), server side, newest first.

query: text to find (Mizito's own in-chat search). from_user: only messages from this person (name/id/"me"). Give query, from_user, or both (both = server filters by text, then sender is checked locally). Paged 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": {
      "chat": "<chat>"
    },
    "name": "search_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
limitNo
queryNo
offsetNo
from_userNo

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 declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds non-obvious context: results are newest first, filtering is server-side but the sender check is applied locally when both filters are given (which can shrink results), and results are paged. It does not mention limits or truncation beyond default page size.

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?

The scope and ordering constraint is front-loaded, and the filter-combination rule follows immediately. The wording is dense but every sentence carries information; only the line-wrapped explanation of local sender checking is slightly awkward.

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?

With an output schema present, return values need not be explained, and the description covers scope, ordering, filter combination, and paging. The remaining minor gap is the meaning and default of 'limit', which the description never mentions.

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 description coverage is 0%, so the description must carry the load, and it does for most parameters: chat accepts id or title, query is Mizito's own in-chat text search, from_user accepts name/id/'me', and offset drives paging with next_offset. Only 'limit' is left unexplained, but overall the meaning added well exceeds the bare schema.

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 inside one chat') plus the scope and ordering ('server side, newest first'), which distinguishes it from a cross-chat search. Siblings such as search_messages and read_chat are not named, so differentiation is inferred 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?

Tells the agent how to combine filters ('Give query, from_user, or both') and how the combination is evaluated, which is real usage guidance. It does not say when to prefer this over search_messages or read_chat, so the choice of tool is left implicit.

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