Skip to main content
Glama

ctxstore — memory that follows you across models

Recent Activity Index

index_recent
Read-onlyIdempotent

Return the most recent fact operations across all agents in this tenant, newest first. Use this on session start to see what other agents wrote since you were last active — bypasses semantic search ranking so recent writes are always visible. Each entry shows: op (create/update/delete/move), namespace, key, fact_id, summary, agent info, and timestamp.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return (default 50, max 200)
since_seqNoOnly return entries with seq > this value (for pagination)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value the annotations cannot: tenant-wide cross-agent scope, deterministic newest-first ordering, and the fact that ranking is bypassed so recent writes are never hidden.

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?

Three sentences, each carrying distinct load: what is returned, when to call it and why it differs from ranked search, and what each entry contains. The usage instruction is front-loaded after the core purpose statement.

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?

With no output schema, the description compensates by enumerating the returned fields (op, namespace, key, fact_id, summary, agent info, timestamp), so the agent knows what it can inspect. Nothing needed to call it correctly is missing for a simple two-optional-parameter read tool.

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%, so both limit and since_seq are fully documented in the schema, establishing the baseline of 3. The description's mention of 'newest first' is consistent with the since_seq pagination model but adds no syntax or format detail beyond the schema.

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 opens with a concrete verb-plus-resource statement — return the most recent fact operations across all agents in the tenant, newest first — and adds the key scope detail (all agents, tenant-wide) that separates it from a per-agent or search-ranked listing. An agent knows exactly what it gets without opening the schema.

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?

It gives a clear trigger — use on session start to see what other agents wrote since you were last active — and explains why it is chosen over semantic search ('bypasses semantic search ranking'), but it does not name a sibling tool such as index_search or state when this should not be used.

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.