Skip to main content
Glama

past.dev

by dev.past
OverviewDiscussionsAdmin

Recall a project's memory

recall_memory
Read-onlyIdempotent

Recalls from one project's memory, as POST /api/v1/recall does: the same arguments, the same refusals and the same answer, each result with its sources. With no identity it reads what the console's Memories screen shows: everything in the project. With an identity it reads as that identity: what the whole project sees, and the audiences that hold the identity. It spends the project's credits where the plan prices a recall, as an API recall does. Needs project Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoThe order of the results after they are chosen: relevance (the default) or chronological.
levelNoThe evidence budget in words: low (8,000 tokens, the default), medium (16,000), high (24,000) or extra-high (32,000). Send this or maxTokens, never both.
limitNoHow many results at most, 1 to 200. 100 when omitted.
queryYesWhat to look for, in plain words.
projectNoThe project's slug, exactly as list_projects returned it. Omit it only when the organization has one live project.
identityNoRead as this identity: the customer's own id for one of their users. Omit it to read everything in the project, as the Memories screen does.
maxTokensNoThe evidence budget in tokens, for a figure no level gives. Send this or level, never both.
occurredToNoThe latest time the evidence may carry (ISO 8601), inclusive.
occurredFromNoThe earliest time the evidence may carry (ISO 8601), inclusive.
queryTimestampNoRecall as of this moment (ISO 8601), with only what was known then. Now when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / identity / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / level / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / project / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / sort / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/destructive/openWorld, but the description adds genuinely non-structured context: it spends the project's credits where the plan prices a recall, and it requires project Read. It also notes results come 'each with its sources'. It does not detail pagination or result shape, keeping it just below the top.

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?

One dense paragraph, front-loaded with the core recall behavior before the scoping, cost and permission clauses. Every sentence contributes (parity, scoping, billing, permission), though the phrasing is slightly ornate and could be tightened.

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?

For a 10-parameter, no-output-schema tool, the description covers the important non-parameter facts an agent needs: mode selection, credit spend, and the project Read requirement. Return content is only briefly characterized ('each result with its sources'), which is acceptable given no output schema but leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantic meaning beyond the schema: what identity scoping actually returns (whole project plus audiences that hold the identity) and that the tool matches the API's arguments, refusals and answer. That is useful interpretation the schema alone does not convey.

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?

States a specific verb and resource ('Recalls from one project's memory') and pins it to the API operation POST /api/v1/recall, so an agent can distinguish it from siblings like ingest_memory or get_timeline. The two operating modes (with vs without identity) are spelled out, which further sharpens what the tool does.

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?

Clearly explains the two modes: with no identity it mirrors the console's Memories screen (everything in the project), with an identity it reads as that identity. It also states the prerequisite ('Needs project Read') and the cost behavior. It stops short of naming explicit alternatives among siblings (e.g., when to prefer get_timeline or find_trace_roots), so it is clear context without exclusions.

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

All past.dev toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources