Skip to main content
Glama

Search MemoryRouter knowledge

search
Read-only

Use this legacy compatibility alias when a client explicitly requests a tool named search. It searches the OAuth-selected MemoryRouter vault without modifying it. For normal ChatGPT recall, prefer search_memories; this tool does not provide citable item permalinks or Company Knowledge fetch support.

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
queryYesNatural-language search query.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / results / items / properties / id / description
      Added value: +"Public memory UUID when indexed; absent for pending-buffer or legacy rows."
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "url"
      -]New value: +[
      +  "title",
      +  "url"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'without modifying it' is largely redundant. However, the description adds real behavioral context beyond the annotations: the vault is OAuth-scoped, and the tool lacks permalink and Company Knowledge fetch capabilities — meaningful limitations for an agent deciding between aliases.

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?

Three tight sentences, front-loaded with the compatibility-alias framing before the alternative and the limitations. Only the 'without modifying it' clause is wasted against the existing readOnly annotation, keeping it just short of ideal.

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 there is no need to describe return values, and the single argument is fully documented in the schema. The description covers scope, the preferred alternative, and key functional gaps; only minor detail about matching behavior across the two aliases is absent.

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?

There is a single parameter with 100% schema coverage and an inline description of 'Natural-language search query'. The tool description adds nothing about query syntax, length limits, or matching behavior, so it meets the baseline of 3 without exceeding it.

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

Purpose5/5

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

The description names the verb and resource ('searches the OAuth-selected MemoryRouter vault') and frames the tool's identity as a 'legacy compatibility alias'. It also explicitly distinguishes it from the sibling 'search_memories', so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit selection rule ('use when a client explicitly requests a tool named search') and an explicit alternative ('For normal ChatGPT recall, prefer search_memories'). It even lists what the tool cannot do (no citable permalinks, no Company Knowledge fetch), which is the kind of exclusion that prevents mis-selection.

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