Skip to main content
Glama
server-noonien

server-noonien

Official

Expand Nodes

expand_nodes
Read-onlyIdempotent

Walk outward from named entities to collect every connected entity and relation within a chosen depth, assembling topic context when neighboring content matters as much as the starting entity.

Instructions

Walk out from the entities you name: every entity within depth hops, with the relations that touch them. Use it instead of read_graph to assemble the context around a topic, and instead of open_nodes when the neighbours' content matters as much as the entity you started from. The walk ignores direction, stops on cycles, and skips names that do not exist rather than failing. When limit binds, truncated is true and the farthest entities are the ones left out.

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": "expand_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoHow many hops to walk, 1 by default and at most 5
limitNoThe most entities to return, 200 by default
namesYesThe entities to start from

Output Schema

NameRequiredDescriptionDefault
entitiesYes
relationsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description discloses traversal semantics that annotations cannot: the walk ignores edge direction, stops on cycles, skips unknown names instead of failing, and marks truncated=true with farthest-first omission when limit binds. These are exactly the behaviors an agent needs to interpret results, though the default depth/limit values are left to the schema.

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?

Three sentences, each load-bearing: traversal shape first, sibling routing second, edge-case and truncation behavior last. No filler, and the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need not be explained, and the description still flags the truncated field's meaning. For a three-parameter read tool, the combination of routing guidance, traversal rules, and failure tolerance leaves nothing an agent needs 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?

Schema coverage is 100%, so the baseline is 3, and the description earns above baseline by explaining what 'limit binds' means for results: the farthest entities are the ones dropped and truncated is set. It adds little for depth beyond restating the hop count already documented in 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 first sentence gives a concrete verb and traversal model ('Walk out from the entities you name: every entity within depth hops, with the relations that touch them'), which tells an agent exactly what comes back. It is explicitly differentiated from both read_graph and open_nodes, so the tool is identifiable without inspecting sibling schemas.

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?

The description names two alternatives and the condition that selects each: use it instead of read_graph to assemble topic context, and instead of open_nodes when neighbour content matters as much as the seed entity. That is explicit routing rather than implied usage.

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