Skip to main content
Glama

Search past Achriom chats

search_conversations
Read-onlyIdempotent

Search the user's past chats with the Achriom librarian inside the Achriom app, by meaning as well as keywords. It does not search Claude's or any other assistant's chat history.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5)
queryYesWhat to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description's one real addition is that retrieval is semantic as well as keyword-based, which is genuinely non-obvious behavior. It says nothing about ranking, result shape, or how `limit` affects retrieval depth.

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 short sentences with zero filler; the positive scope and the semantic matching claim are front-loaded, with the disambiguation clause immediately after. Nothing needs trimming.

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-only search tool with full schema coverage and no output schema, the description supplies the essential scope and matching mode. The remaining gap is routing against the numerous other search tools, which the definition does not address.

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 100% for both parameters, so the schema already explains `query` and `limit` including the default of 5. The description adds no syntax, format, or query-construction guidance beyond that, making the baseline 3 appropriate.

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 uses a specific verb ('Search') plus a precisely bounded resource (past chats with the Achriom librarian inside the Achriom app), and adds a matching-mode detail ('by meaning as well as keywords'). It implicitly separates itself from the generic `search` and `search_library` siblings by scoping to Achriom chat history, though it never names those siblings explicitly.

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 negative clause ('It does not search Claude's or any other assistant's chat history') gives a useful when-not boundary. However, there is no explicit statement of when to reach for this versus the many other `search_*` siblings, so an agent must infer the selection rule.

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