Penfield Memory

recall

Read-only

Recall relevant information.

Uses hybrid search to find relevant memories, documents, and connections.

Args:
    query: What to search for
    source_type: Optional filter ('memory', 'document', or None for all)
    tags: Optional list of tags to filter by (OR logic - memories with ANY of these tags)
    start_date: Optional filter for memories created on or after this date (ISO 8601: '2025-01-01')
    end_date: Optional filter for memories created on or before this date (ISO 8601: '2025-01-09')
    limit: Maximum results to return (default 10, max 100)
    include_inactive: Include superseded/contradicted memories (default: false)
    ctx: MCP context (automatically provided)

Returns:
    Dict with success status, query, found count, and memories list

Examples:
    >>> await recall("Python error handling")
    {'success': True, 'found': 3, 'memories': [...]}

    >>> await recall("documentation", source_type="document", limit=5)
    {'success': True, 'found': 2, 'memories': [...]}

    >>> await recall("debugging", tags=["python"])
    {'success': True, 'found': 2, 'memories': [...]}  # Only memories tagged with 'python'

    >>> await recall("project updates", start_date="2025-01-01", end_date="2025-01-07")
    {'success': True, 'found': 5, 'memories': [...]}  # Only memories from that week

Note: Document chunks include surrounding context automatically (2 chunks before/after).
Document results also include source_type="document", filename, document_title, and document_id
when available, making it easy to identify which document a result came from.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No
`limit`	No
`query`	Yes
`end_date`	No
`start_date`	No
`source_type`	No
`include_inactive`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 1, 2026

addedInput schema / properties / include_inactive

Added value: +{
+  "default": false,
+  "title": "Include Inactive",
+  "type": "boolean"
+}

First observedMar 16, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations indicate read-only, open-world. Description adds significant behavioral details: hybrid search method, filter options, default and max limit, date format, include_inactive flag, and document chunk context. No contradictions.

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?

Well-structured with title, args list, returns, examples, and notes. Front-loaded purpose. Some redundancy with schema but informative. Could be slightly more concise.

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?

Comprehensive coverage: all 7 parameters explained, return format detailed, examples provided, and special notes about document context. Given annotations and output schema, no gaps remain.

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

Parameters5/5

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

Schema description coverage is 0%, but the description thoroughly explains each parameter with examples, including OR logic for tags, date format, limit defaults, and the include_inactive flag. Adds meaning beyond schema names.

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 clearly states the tool recalls information using hybrid search, specifying resources like memories and documents. However, it does not differentiate from the sibling tool 'search', which may have similar functionality.

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?

Examples show when to use the tool, but no explicit guidance on when not to use it or alternatives. Implied usage from examples, but lacks exclusions or comparisons with siblings.

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

All Penfield Memory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.