memory-bank-mcp

Overview Schema Source Related Servers Discussions Admin

graph_open_nodes

Retrieve a subgraph of specified entities and their connected nodes from the knowledge graph, enabling exploration of related project context, decisions, and progress.

Instructions

Open specific nodes and their neighborhood. Returns a subgraph with the requested entities and their connections.

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": {
      "nodes": "<nodes>"
    },
    "name": "graph_open_nodes"
  }
}

Input Schema

Name	Required	Description
`storeId`	No	Optional store ID to target a specific registered store instead of the active one
`nodes`	Yes	Array of entity names or IDs to open
`depth`	No	Neighborhood depth (1 or 2, default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Apr 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions returning a subgraph but fails to specify if the operation is read-only, if it modifies state, or what happens when nodes are not found. This is insufficient for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no unnecessary words. It is appropriately front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema and annotations, the description is minimally adequate. It covers the basic purpose but does not explain return values, error cases, or side effects, which are needed for a complete understanding.

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

Parameters3/5

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

The input schema has 100% coverage, so the description adds minimal value. It reiterates that 'nodes' are entity names/IDs and 'depth' is neighborhood depth, which is already in the schema. The description does not enrich the parameters further.

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 action (open), the resource (specific nodes and their neighborhood), and the output (subgraph with connections). This effectively distinguishes it from sibling tools like graph_search or graph_delete_entity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as graph_search. It lacks explicit context for the appropriate use case, leaving the agent without decision-making support.

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