Skip to main content
Glama

query_episodes

Retrieve episodic memories from a vault, filtering by entity or time to see current, past, or historically known facts. Rank results by query text or return the newest.

Instructions

Retrieve episodes from an episodic vault. By default only statements that still hold are returned. Filter by entity for 'everything about X', pass valid_at to ask what was true at a past moment, or known_at to ask what the vault had already learned by then. Query text is optional and ranks results; without it the newest come first.

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": {
      "vault_name": "<vault_name>"
    },
    "name": "query_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
entitiesNo
known_atNo
order_byNo
valid_atNo
vault_nameYes
include_closedNo

Output Schema

NameRequiredDescriptionDefault
queryNo
resultsYes
order_byYes
vault_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious defaults: only currently-holding statements are returned and results are newest-first when query text is absent. It omits what include_closed does, how limit interacts with ranking, and any permission or vault-scoping behavior, which keeps it out of the 5 range.

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?

Four sentences, front-loaded with purpose and default behavior, then the filter options. The 'everything about X' framing earns its space as a usage cue; nothing is padded or redundant.

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?

An output schema exists, so return values need not be explained, and the temporal semantics are handled well. However, an 8-parameter read tool with zero annotation coverage and 0% schema descriptions leaves include_closed and limit behavior undocumented, which is a meaningful gap for callers tuning result sets.

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 0%, so the description must compensate, and it explains only the semantically tricky parameters (entities, valid_at, known_at, query, and the default ordering). Three of eight parameters — limit, include_closed, and vault_name — are never mentioned, leaving their meaning entirely to a bare 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?

The description opens with a specific verb and resource: 'Retrieve episodes from an episodic vault.' That is clear enough to distinguish it from write/modify siblings like write_episode or invalidate_episode, but it never contrasts with the closely related 'query' or 'episode_history' tools, so the boundary requires inference.

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 concrete conditional guidance: use entity filters for 'everything about X', valid_at for truth at a past moment, known_at for what was known by then. It stops short of naming an alternative tool or stating when not to use this one, so it lands just below the top mark.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.