Skip to main content
Glama
Sign In
Fodda Context Layer

Fodda Context Layer

by piers-fawkes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_neighbors

Read-onlyIdempotent

Discover related brands, technologies, locations, and cross-domain links around a trend by traversing a knowledge graph from a seed node. Maps connected entities for deeper context.

Instructions

Discover what's connected to a specific trend — related brands, technologies, locations, and cross-domain links. Returns curated editorial connections between trends. Use after search_graph to map the territory around a trend, find which brands are connected, or understand cross-domain relationships. Requires node_id from a prior search_graph result. (1-hop graph relationship traversal from seed node in Neo4j.)

Input Schema

NameRequiredDescriptionDefault
depthNoTraversal depth (default 1, max 2)
limitNoMaximum results (default 50)
userIdNoOptional user identifier for trial usage tracking.
graphIdYesThe graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'automotive-color-trends', 'alyson-stevens-macro', 'dentsu-creative-marketing', 'pwc/sxsw-2026-key-insights', 'green-house/thrive-report', 'michaels-2026-creativity-trend-report', 'delta/the-connection-index'
directionNoTraversal direction: 'out' (default) follows outgoing edges, 'in' follows incoming edges
seed_node_idsYesArray of node IDs to start traversal from. MUST be actual node_id values from a prior search_graph result (e.g. ["2507.0"]). Node IDs are NOT sequential integers — do NOT guess or invent IDs like "1", "2", "3". Always call search_graph first to obtain valid IDs.
relationship_typesNoFilter by relationship types: 'EVIDENCED_BY', 'RELATED_TO', 'SEMANTICALLY_SIMILAR', 'ASSOCIATED_BRAND', 'MENTIONS_BRAND', 'IN_LOCATION'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.3.3
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / direction
      Added value: +{
+  "description": "Traversal direction: 'out' (default) follows outgoing edges, 'in' follows incoming edges",
+  "enum": [
+    "in",
+    "out"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / graphId / description
      Previous value: -"The graph ID"New value: +"The graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'automotive-color-trends', 'alyson-stevens-macro', 'dentsu-creative-marketing', 'pwc/sxsw-2026-key-insights', 'green-house/thrive-report', 'michaels-2026-creativity-trend-report', 'delta/the-connection-index'"
    • changedInput schema / properties / relationship_types / description
      Previous value: -"Filter by relationship types"New value: +"Filter by relationship types: 'EVIDENCED_BY', 'RELATED_TO', 'SEMANTICALLY_SIMILAR', 'ASSOCIATED_BRAND', 'MENTIONS_BRAND', 'IN_LOCATION'"
    • changedInput schema / properties / seed_node_ids / description
      Previous value: -"Array of node IDs to start traversal from"New value: +"Array of node IDs to start traversal from. MUST be actual node_id values from a prior search_graph result (e.g. [\"2507.0\"]). Node IDs are NOT sequential integers — do NOT guess or invent IDs like \"1\", \"2\", \"3\". Always call search_graph first to obtain valid IDs."
    • changedInput schema / properties / userId / description
      Previous value: -"Unique identifier for the user (Required)"New value: +"Optional user identifier for trial usage tracking."
    • changedInput schema / required
      Previous value: -[
-  "graphId",
-  "seed_node_ids",
-  "userId"
-]New value: +[
+  "graphId",
+  "seed_node_ids"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "edges": {
-      "description": "Array of relationships between nodes",
-      "type": "array"
-    },
-    "nodes": {
-      "description": "Array of neighboring nodes",
-      "type": "array"
-    },
-    "usage": {
-      "properties": {
-        "total_billable_units": {
-          "type": "number"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv1.3.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=false, so the safety profile is covered. The description adds genuinely useful context beyond that: results are 'curated editorial connections', the underlying store is Neo4j, and it is a 1-hop traversal from the seed node.

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?

Four sentences, front-loaded with the outcome and followed by usage and the structural note. Slightly dense and the parenthetical about Neo4j 1-hop traversal is somewhat redundant with the usage sentence, but there is no filler.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so adequately ('curated editorial connections'). Combined with the prerequisite and the traversal semantics, an agent has what it needs to call this correctly; only a note on result shape/size would push it higher.

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 every parameter is already documented in the schema, including depth/limit defaults and the direction semantics. The description only reiterates the node_id prerequisite, which the schema also states emphatically, so it adds little beyond the structured fields.

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 names a specific verb and resource ('Discover what's connected to a specific trend') and enumerates the kinds of results (related brands, technologies, locations, cross-domain links). It also distinguishes itself from the sibling search_graph by positioning itself as the follow-up relational traversal step, so an agent can tell them apart.

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

Usage Guidelines4/5

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

It explicitly says to use it after search_graph and lists concrete intents (map territory, find connected brands, understand cross-domain relationships), plus a prerequisite (node_id from a prior search_graph result). It lacks explicit when-not-to-use guidance or named alternative tools beyond the prerequisite, so it stops short of a 5.

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