Skip to main content
Glama

ctxstore — memory that follows you across models

Search Activity Index

index_search
Read-onlyIdempotent

Filtered search over the tenant activity index. Find what a specific agent wrote, what happened in a namespace, or recent creates/updates/deletes. Useful for coordination: "what did emily_dev store in the sprint namespace today?"

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "index_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoFilter by operation: create, update, delete, or move
limitNoMax entries to return (default 100)
namespaceNoFilter by namespace (e.g. 'sprint', 'default')
since_seqNoOnly return entries with seq > this value
agent_nameNoFilter by agent name from agent_signature

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered without the text. The description adds the coordination framing but says nothing about result ordering, the default cap of 100 entries, or how since_seq enables incremental polling — the behaviors an agent actually needs to interpret results.

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?

Two sentences, front-loaded with the core capability followed by concrete use cases; no filler. The closing quote slightly restates filters already named in sentence one, a minor redundancy.

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

Completeness3/5

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

With five optional filters, no output schema, and no required parameters, the agent still lacks knowledge of what an entry looks like, whether results are ordered by seq, and whether the limit truncates silently. Annotations cover the safety dimension, but return-shape and pagination behavior are left 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 coverage is 100%, so the schema already documents all five parameters and the op enum, making 3 the baseline. The description adds real-world meaning to agent_name, namespace, and the operation filter through its example queries, but leaves limit and since_seq (the least self-explanatory parameters) entirely to the schema.

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 ("filtered search over the tenant activity index") and enumerates the three queryable dimensions: agent, namespace, and operation. It does not explicitly contrast itself with the close siblings index_recent or search_context, so an agent must infer the boundary from those tools' own definitions.

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 worked example ("what did emily_dev store in the sprint namespace today?") conveys the intended coordination use case and implicitly shows that filters combine. However, there is no explicit when-to-use versus index_recent / index_stats / search_facts routing, and no statement of when-not to use it.

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.