Skip to main content
Glama

Coline

Search messages

search_messages
Read-onlyIdempotent

Searches the person's messages, files, people and channels in Messages, with filters for who, where, when and what the message has.

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": {
      "workspace": "<workspace>",
      "query": "<query>",
      "resultTypes": "<resultTypes>",
      "from": "<from>",
      "in": "<in>",
      "with": "<with>",
      "has": "<has>",
      "fileTypes": "<fileTypes>",
      "reactions": "<reactions>"
    },
    "name": "search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
inYesConversations it's in.
hasYes
fromYesPeople who wrote it.
sortNo
withYes
afterNo
limitNo
queryYes
beforeNo
cursorNo
fileTypesYes
reactionsYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
containerIdNo
resultTypesYes
containerTypeNo
threadRootMessageIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that: no mention of result caps (limit max 50), sorting behavior (relevance vs recent), cursor-based pagination, or what a search over multiple result types returns. For a 17-parameter search surface this leaves real behavioral questions unanswered.

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?

A single well-formed sentence with the resource scope front-loaded and no filler. It is dense but every clause carries meaning; the only cost is that compression leaves no room for the guidance the tool actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 parameters, 9 of them required, and only 18% schema coverage, the description is far too thin for the decision surface being exposed. An output schema exists so return values need not be described, but the agent still cannot learn from this definition how required array filters like resultTypes, from, in, with and has behave, or how pagination and result ordering work.

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 description coverage is only 18%, so the description must compensate, and it does partially by framing the filters as who (from/with), where (in), when (after/before) and what the message has (has). However, ten-plus parameters remain unmapped — resultTypes with a 14-value enum, fileTypes, reactions, sort, limit, cursor, containerId, containerType, threadRootMessageId, workspace — so much of the search surface has no explanation anywhere.

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?

Names a specific verb (Searches) and a scoped resource set (messages, files, people and channels in Messages), which is enough to separate it from non-Messages search tools like search_mail or search_events. It stops short of naming any sibling explicitly, so the differentiation is inferred from the product scope rather than stated.

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?

Usage is implied by 'Searches ... with filters for who, where, when and what the message has', which tells the agent the tool is filter-driven. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for broader cross-product search, so the agent must infer routing from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources