Skip to main content
Glama

Penfield Memory

by io.github.penfieldlabs
OverviewDiscussionsAdmin

disconnect

Destructive
Remove a connection between memories.

Deletes the relationship between two memories in the knowledge graph.

Args:
    from_memory: Source memory UUID
    to_memory: Target memory UUID
    ctx: MCP context (automatically provided)
    
Returns:
    Dict with success status and disconnected memory IDs
    
Examples:
    >>> await disconnect("uuid-abc", "uuid-def")
    {'success': True, 'from_id': '...', 'to_id': '...'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_memoryYes
from_memoryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already indicate destructiveHint=true, and the description confirms it by stating 'Deletes'. The description adds no further behavioral context beyond what annotations suggest, such as specifics about what gets destroyed or side effects.

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 a brief main sentence followed by Args, Returns, and Examples sections. It is relatively concise, though including the ctx parameter adds a small amount of noise.

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 two simple parameters and the existence of an output schema, the description covers the essential aspects. It explains both parameters, provides a return format, and includes an example. Minor gaps remain in usage guidelines.

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?

The schema has no descriptions for parameters (coverage 0%), so the description must compensate. It does so by explaining that 'from_memory' is the source UUID and 'to_memory' is the target UUID, and provides an example showing placeholder values.

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 with the verb 'Remove' and the resource 'connection between memories'. It explicitly says it 'Deletes the relationship between two memories', making it distinct from the sibling tool 'connect'.

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. While the sibling 'connect' implies this is for removal, no direct guidance is provided about prerequisites, conditions, or when to prefer one over the other.

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