NetworkX MCP Server

get_neighbors

Retrieve all adjacent nodes for a given node in a graph, enabling analysis of connections and relationships.

Instructions

Get all neighbors of a node

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": {
      "graph": "<graph>",
      "node": "<node>"
    },
    "name": "get_neighbors"
  }
}

Input Schema

Name	Required	Description	Default
`node`	Yes
`graph`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Aug 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Get all neighbors' without explaining whether this includes incoming/outgoing edges, output format, error handling for missing nodes or graphs, or whether the result is ordered.

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

Conciseness3/5

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

The single-sentence description is concise and front-loaded, but it is under-specified and omits essential behavioral context, making it less useful than an appropriately sized description that includes trade-offs or edge cases.

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

Completeness2/5

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

For a simple get operation, the description is too sparse. It does not cover return value, default behavior, or error conditions, making it incomplete for an agent to invoke correctly without additional context.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond param names. It never explains the 'graph' parameter or what values are expected for 'node', leaving the agent to infer semantics solely from the identifier names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and the resource ('neighbors of a node'), making the tool's purpose specific and distinguishable from sibling graph algorithms. It lacks nuance about directed vs. undirected graphs, but the core purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like degree_centrality or connected_components. There is no mention of directed graph behavior, preconditions (e.g., node existence), or exclusions.

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