Skip to main content
Glama
Plain Text Memory MCP

Plain Text Memory MCP

Open entities

open_nodes
Read-onlyIdempotent

Open entities by exact name to retrieve their relations and access logs; optionally include superseded notes. Use it to inspect a specific memory-graph entity and all its connections.

Instructions

Open entities by exact name.

Returns the named entities and every relation that touches them; a relation's other end may be outside the results. Names that do not exist are ignored. Struck-through facts are hidden unless include_superseded is set. Each open is logged, so search ranks often-opened entities higher. To find entities by keyword, see search_nodes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "<names>"
    },
    "name": "open_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesExact names of the entities to open.
include_supersededNoAlso return notes that were struck through, with superseded_at and replaced_by; hidden by default.

Output Schema

NameRequiredDescriptionDefault
entitiesYes
relationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.4.0
    • addedInput schema / properties / include_superseded
      Added value: +{
      +  "default": false,
      +  "description": "Also return notes that were struck through, with superseded_at and replaced_by; hidden by default.",
      +  "title": "Include Superseded",
      +  "type": "boolean"
      +}
    • changedOutput schema / $defs / EntityRecord / description
      Previous value: -"One entity line of the memory file."New value: +"One entity as JSON, with its notes."
    • addedOutput schema / $defs / EntityRecord / properties / notes
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/NoteRecord"
      +  },
      +  "title": "Notes",
      +  "type": "array"
      +}
    • removedOutput schema / $defs / EntityRecord / properties / observations
      Removed value: -{
      -  "items": {
      -    "$ref": "#/$defs/ObservationRecord"
      -  },
      -  "title": "Observations",
      -  "type": "array"
      -}
    • changedOutput schema / $defs / EntityRecord / required
      Previous value: -[
      -  "type",
      -  "name",
      -  "entityType",
      -  "added_at",
      -  "agent",
      -  "observations"
      -]New value: +[
      +  "type",
      +  "name",
      +  "entityType",
      +  "added_at",
      +  "agent",
      +  "notes"
      +]
    • addedOutput schema / $defs / NoteRecord
      Added value: +{
      +  "description": "One note as JSON, inside an entity's notes list.",
      +  "properties": {
      +    "added_at": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Added At"
      +    },
      +    "agent": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Agent"
      +    },
      +    "path": {
      +      "title": "Path",
      +      "type": "string"
      +    },
      +    "replaced_by": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Replaced By"
      +    },
      +    "superseded_at": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Superseded At"
      +    },
      +    "text": {
      +      "title": "Text",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "added_at",
      +    "agent"
      +  ],
      +  "title": "NoteRecord",
      +  "type": "object"
      +}
    • removedOutput schema / $defs / ObservationRecord
      Removed value: -{
      -  "description": "One observation as JSON, inside an entity's observations list.",
      -  "properties": {
      -    "added_at": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "title": "Added At"
      -    },
      -    "agent": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "title": "Agent"
      -    },
      -    "edited_at": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "title": "Edited At"
      -    },
      -    "edited_by": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "title": "Edited By"
      -    },
      -    "text": {
      -      "title": "Text",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "text",
      -    "added_at",
      -    "agent"
      -  ],
      -  "title": "ObservationRecord",
      -  "type": "object"
      -}
    • changedOutput schema / $defs / RelationRecord / description
      Previous value: -"One relation line of the memory file."New value: +"One relation as JSON."
  2. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that relations touching the entities are returned and may dangle, that unknown names are silently ignored, that struck-through facts are hidden unless include_superseded is set, and that opens are logged so ranking changes. That logging side effect is exactly the kind of context annotations cannot express.

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?

Front-loaded with the purpose, then the return shape, then edge cases and the alternative. Five short sentences that each carry information, though the superseded sentence overlaps with the schema's own parameter description.

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?

Covers the graph semantics (relations with possibly external endpoints), missing-name handling, and visibility of superseded facts; an output schema is present, so return-value detail is not needed. Nothing an agent needs in order to call it correctly is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning about include_superseded's effect on which struck-through facts appear. It does not add syntax or limits for the names array beyond what the schema already says.

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 ('Open entities by exact name') and immediately contrasts with the keyword-based sibling search_nodes. An agent can distinguish this from recall, stamp_notes and search_nodes without opening a schema.

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 names the alternative and the condition that selects it ('To find entities by keyword, see search_nodes'), plus the exact-name constraint that governs correct use. Nothing about tool selection is left to inference.

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

Deploy Server

Other Tools