Skip to main content
Glama

ctxstore — memory that follows you across models

Search Conversations

search_context
Read-onlyIdempotent

Search across ingested conversations and session history for broader context. Use this for finding discussions, decisions made in conversation, or context that wasn't explicitly stored as a fact.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language search query
top_kNoNumber of results (default 20, max 100)
sourceNoFilter by source: 'chatgpt' or 'claude'
days_backNoOnly search within last N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful scope note that only *ingested* conversation and session history is searched, but says nothing about ranking, result shape, or cost of a broad query.

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 sentences, no filler, with the capability statement front-loaded and the usage cue immediately after. Every clause contributes either scope or routing information.

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 four well-documented parameters and no output schema, the description covers what an agent needs to decide to call it and what domain it searches. It falls just short of complete by not describing how results come back (snippets, timestamps, ranking) for a search tool whose output is unspecified.

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%, including the enum on source and the default/max on top_k, so the schema carries parameter meaning on its own. The description adds no syntax, query-phrasing hints, or guidance on combining days_back with source, so baseline 3 applies.

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 across ingested conversations and session history. It also implicitly distinguishes itself from the fact-storage siblings by scoping to material 'that wasn't explicitly stored as a fact', though it never names search_facts directly.

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

Usage Guidelines4/5

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

The second sentence gives concrete triggers: finding discussions, decisions made in conversation, or non-fact context. It implicitly excludes the fact-lookup path but does not explicitly name an alternative tool, so the routing signal is clear but not fully enumerated.

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.