Penfield Memory

explore

Read-only

Explore connections from a memory.

Traverses the knowledge graph to find related concepts, following
relationships up to the specified depth.

Args:
    start_memory: Starting memory UUID
    max_depth: How deep to traverse (default 3, max 10)
    relationship_types: Filter by specific relationship types (optional)
    ctx: MCP context (automatically provided)
    
Returns:
    Dict with paths found, max depth reached, and path details
    
Examples:
    >>> await explore("uuid-123", max_depth=2)
    {'success': True, 'paths_found': 5, 'max_depth_reached': 2, 'paths': [...]}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`max_depth`	No
`start_memory`	Yes
`relationship_types`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, but the description adds behavioral details: traversal depth limits (max 10), return format (dict with paths_found, max_depth_reached, paths), and an example. No contradiction with 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?

The description is well-structured with Args, Returns, and Examples sections. It is clear and not overly long, though some redundancy exists (e.g., repeating types in Examples).

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?

Given the presence of output schema and annotations, the description covers behavior, parameters, and return basics adequately. However, it lacks details on relationship_types format or how paths are structured, slightly limiting completeness.

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?

With 0% schema description coverage, the description fully explains each parameter: start_memory (UUID), max_depth (default 3, max 10), relationship_types (optional filter), and ctx (automatically provided). This adds significant meaning 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 clearly states the tool's purpose: 'Explore connections from a memory. Traverses the knowledge graph to find related concepts.' It distinguishes itself from sibling tools like 'search' and 'recall' by specifying graph traversal.

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?

The description does not explicitly state when to use this tool versus alternatives. It provides examples but no guidance on context or exclusions, leaving usage implied.

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.