Skip to main content
Glama
piers-fawkes

Fodda Context Layer

by piers-fawkes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_node

Read-onlyIdempotent

Retrieve a trend's full profile—lifecycle stage, signal strength, geographic scope, and all properties—using a node_id from a prior search_graph summary. Use for deeper detail on a single trend.

Instructions

Get the full profile of a specific trend — detailed description, lifecycle stage (emerging/building/mature), signal strength, geographic scope, and all properties. Use when you need deeper detail on a single trend after search_graph returned a summary. Requires node_id from a prior search_graph result. (Direct Neo4j node metadata lookup by ID.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe node_id from a prior search_graph result (e.g. '2507.0'). MUST come from the search result's node_id field. Node IDs are NOT sequential integers — do NOT guess or invent IDs like '1', '2', '3'. Do NOT pass the trend name.
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'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.3.3
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • 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 / nodeId / description
      Previous value: -"The ID of the node"New value: +"The node_id from a prior search_graph result (e.g. '2507.0'). MUST come from the search result's node_id field. Node IDs are NOT sequential integers — do NOT guess or invent IDs like '1', '2', '3'. Do NOT pass the trend name."
    • 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",
-  "nodeId",
-  "userId"
-]New value: +[
+  "graphId",
+  "nodeId"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "display": {
-      "description": "Display name of the node",
-      "type": "string"
-    },
-    "id": {
-      "description": "Node ID",
-      "type": "string"
-    },
-    "labels": {
-      "description": "Array of node labels/types",
-      "type": "array"
-    },
-    "properties": {
-      "description": "Key-value properties of the node",
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv1.3.2

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that this is a 'Direct Neo4j node metadata lookup by ID', implying a raw, non-enriched read, but says nothing about failure behavior for invalid IDs, cost, or limits.

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?

Front-loaded with the payload contents, then usage, then the prerequisite. The trailing parenthetical on Neo4j is slightly awkward and could be folded in earlier, but every sentence carries information.

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 enumerates the return fields and the required input provenance, which is the main thing an agent needs. Remaining gaps (error handling for bad IDs, response shape details) are minor for a simple read-by-ID tool.

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% and the nodeId/graphId descriptions already carry the critical warnings (non-sequential IDs, do not pass trend name, use list_graphs for graphId). The description only restates the node_id provenance requirement, so the schema does the heavy lifting; baseline 3 applies.

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?

States a specific verb and resource ('Get the full profile of a specific trend') and enumerates the returned fields (description, lifecycle stage, signal strength, geographic scope). It explicitly differentiates itself from the sibling search_graph by contrasting a summary with deep single-node detail.

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?

Gives an explicit trigger ('Use when you need deeper detail on a single trend after search_graph returned a summary') plus the prerequisite that node_id must come from a prior search_graph result. The alternative tool and the condition that selects it are both named, leaving nothing to inference.

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