Skip to main content
Glama

search

Read-onlyIdempotent

Find messages across the whole room history using accent- and case-insensitive matching where every word must appear. Narrow results by topic or sender, ranked by relevance and recency, without marking anything read.

Instructions

Search the whole room history (accent and case insensitive; every word must match; "in quotes" = exact phrase). Most relevant then most recent first; nothing is marked read.

Args: query: words or "phrase" to find. topic: limit to one topic (optional). sender: limit to one sender: "claude", "antigravity" or "codex" (optional). limit: number of results returned (1 to 100).

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
limitNo
queryYes
topicNo
senderNo

Output Schema

NameRequiredDescriptionDefault
hitsYes
noteYes
totalYes
statusYes
late_noteNo
late_repliesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.8.7
    • addedOutput schema / $defs
      Added value: +{
      +  "Attachment": {
      +    "properties": {
      +      "mime": {
      +        "title": "Mime",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "path": {
      +        "title": "Path",
      +        "type": "string"
      +      },
      +      "size": {
      +        "title": "Size",
      +        "type": "integer"
      +      }
      +    },
      +    "title": "Attachment",
      +    "type": "object"
      +  },
      +  "RenderedMessage": {
      +    "properties": {
      +      "attachments": {
      +        "items": {
      +          "$ref": "#/$defs/Attachment"
      +        },
      +        "title": "Attachments",
      +        "type": "array"
      +      },
      +      "cancelled": {
      +        "title": "Cancelled",
      +        "type": "string"
      +      },
      +      "created": {
      +        "title": "Created",
      +        "type": "string"
      +      },
      +      "due": {
      +        "title": "Due",
      +        "type": "string"
      +      },
      +      "from": {
      +        "title": "From",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "info": {
      +        "title": "Info",
      +        "type": "boolean"
      +      },
      +      "quality": {
      +        "title": "Quality",
      +        "type": "string"
      +      },
      +      "reply_to": {
      +        "title": "Reply To",
      +        "type": "string"
      +      },
      +      "state": {
      +        "title": "State",
      +        "type": "string"
      +      },
      +      "text": {
      +        "title": "Text",
      +        "type": "string"
      +      },
      +      "to": {
      +        "title": "To",
      +        "type": "string"
      +      },
      +      "topic": {
      +        "title": "Topic",
      +        "type": "string"
      +      },
      +      "vote": {
      +        "title": "Vote",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "from",
      +      "to",
      +      "topic",
      +      "created",
      +      "text"
      +    ],
      +    "title": "RenderedMessage",
      +    "type": "object"
      +  },
      +  "SearchHit": {
      +    "properties": {
      +      "created": {
      +        "title": "Created",
      +        "type": "string"
      +      },
      +      "from": {
      +        "title": "From",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "reply_to": {
      +        "title": "Reply To",
      +        "type": "string"
      +      },
      +      "score": {
      +        "title": "Score",
      +        "type": "number"
      +      },
      +      "snippet": {
      +        "title": "Snippet",
      +        "type": "string"
      +      },
      +      "to": {
      +        "title": "To",
      +        "type": "string"
      +      },
      +      "topic": {
      +        "title": "Topic",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "from",
      +      "to",
      +      "topic",
      +      "created",
      +      "score",
      +      "snippet"
      +    ],
      +    "title": "SearchHit",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / hits
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/SearchHit"
      +  },
      +  "title": "Hits",
      +  "type": "array"
      +}
    • addedOutput schema / properties / late_note
      Added value: +{
      +  "title": "Late Note",
      +  "type": "string"
      +}
    • addedOutput schema / properties / late_replies
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/RenderedMessage"
      +  },
      +  "title": "Late Replies",
      +  "type": "array"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "title": "Note",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "title": "Result",
      -  "type": "string"
      -}
    • addedOutput schema / properties / status
      Added value: +{
      +  "const": "success",
      +  "title": "Status",
      +  "type": "string"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "title": "Total",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "status",
      +  "total",
      +  "hits",
      +  "note"
      +]
    • changedOutput schema / title
      Previous value: -"searchOutput"New value: +"SearchOut"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the bar is lower. The description adds valuable behavior beyond annotations: accent/case insensitivity, every-word matching, quoted exact-phrase behavior, ranking order, and the fact that nothing is marked read.

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?

The description is front-loaded with the core search semantics, then uses a compact Args list for parameters. Every sentence carries useful information and there is no redundant filler.

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

Completeness5/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 shape need not be described. Combined with annotations covering safety and the description covering search matching, ordering, side effects, and all four parameters, this is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 parameter meaning, and it does. It explains query syntax, topic as a single-topic filter, sender with accepted values, and limit as a 1–100 result count.

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?

The description states a specific verb and resource: "Search the whole room history." It adds scope details such as searching all history and not marking anything read, but does not explicitly differentiate itself from sibling tools like read or inbox.

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 the description: search room history with optional topic and sender filters. It does not state when to use this tool instead of read, inbox, or other siblings, nor does it describe exclusions.

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