Skip to main content
Glama

Penfield Memory

by io.github.penfieldlabs
OverviewDiscussionsAdmin

fetch

Read-only
[ChatGPT Connector compat] Fetch memory by ID.

Exists to satisfy ChatGPT Deep Research's required `search`/`fetch` tool
contract. Native MCP clients should fetch via `recall` + memory_id, or
use the API's GET /memories/{id} endpoint directly.

Returns a single memory with citation support (id, title, url, text fields).

Args:
    id: Memory UUID to fetch
    ctx: MCP context

Returns:
    Dict with id, title, url, text, metadata fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true. Description adds that it returns a single memory with citation support (id, title, url, text fields), and explains the tool's purpose beyond annotations.

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 clear sections: purpose, rationale, args, returns. Slightly lengthy but every sentence is informative. Could be 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?

For a simple read-only tool with one parameter and an output schema, the description covers purpose, usage context, return fields, and rationale. Complete and sufficient.

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?

Only one parameter (id) with 0% schema description coverage. Description adds 'Memory UUID to fetch', which clarifies the expected input beyond the raw schema type. Good but minimal additional context.

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 clearly states the tool fetches a memory by ID, distinguishes it from native alternatives like recall, and specifies its role for ChatGPT Connector compatibility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (ChatGPT Deep Research requirement) and when not to (native MCP clients should use recall or API endpoint). Provides clear alternatives.

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

All Penfield Memory toolsInspect
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.

Resources