Skip to main content
Glama

Lattice

by io.namiq
OverviewDiscussionsAdmin

List linked nodes

graph_neighbors
Read-onlyIdempotent

Directly connected nodes with each link's verb, source, confidence and whether it is declared or inferred. Declared and cross-source links come first. If the answer has truncated: true, pass its next_cursor as cursor to continue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesThe uid of the node whose links to list, from graph_lookup, graph_search or graph_node.
verbNoOptional upper-case relationship verb to keep, for example EXPLOITS, DETECTS or USES. The valid verbs are listed by graph_meta.
labelNoOptional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.
limitNoMaximum links to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped.
cursorNoContinuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page.
directionNoWhich links to follow: out (from this node), in (to this node) or both.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Continuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page."
    • addedInput schema / properties / direction / description
      Added value: +"Which links to follow: out (from this node), in (to this node) or both."
    • addedInput schema / properties / label / description
      Added value: +"Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum links to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped."
    • addedInput schema / properties / uid / description
      Added value: +"The uid of the node whose links to list, from graph_lookup, graph_search or graph_node."
    • addedInput schema / properties / verb / description
      Added value: +"Optional upper-case relationship verb to keep, for example EXPLOITS, DETECTS or USES. The valid verbs are listed by graph_meta."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: result ordering (declared and cross-source links first) and the truncation/next_cursor continuation protocol. It omits detail on confidence semantics and result size behavior.

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 tight sentences with no waste, and the most important content (what is returned and in what order) is front-loaded before the pagination mechanics.

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?

With no output schema, the description usefully names the returned fields and the truncation contract, which is what an agent needs to page correctly. Remaining gaps, such as confidence scale or whether duplicate links can appear, are minor.

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?

Schema description coverage is 100%, so the schema fully documents uid, verb, label, limit, cursor and direction. The description restates the cursor/truncated relationship and the returned fields but adds no filter syntax or format detail beyond the schema.

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?

States a specific resource and scope: 'directly connected nodes' with each link's verb, source, confidence and declared/inferred status. It is clear this is a single-hop neighbor listing rather than a search or path tool. It does not, however, explicitly name a sibling to contrast against.

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?

Usage is only implied by the resource itself (list links for a node). There is no statement of when to prefer this over graph_path or graph_search, nor any prerequisite guidance beyond the uid source noted in the schema. The pagination instruction is operational rather than selection guidance.

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

All Lattice 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