Skip to main content
Glama
piers-fawkes

Fodda Context Layer

by piers-fawkes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_label_values

Read-onlyIdempotent

List all values for a graph label, such as Brand, Location, Technology, Audience, or Trend, to explore graph contents and retrieve complete deterministic lists.

Instructions

List all brands, locations, technologies, audiences, or trends within a specific knowledge graph. Use to explore what a graph contains — e.g., "what brands are in the retail graph?" or "what locations does the fashion graph cover?". To get a complete list of every trend in a graph, call with label="Trend" — this returns the full deterministic list, useful for industry-report graphs where search may return partial results. (Graph taxonomy label value lookup.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesThe label to fetch values for (e.g., 'Brand', 'Location', 'Technology', 'Audience', 'RetailerType', 'Trend')
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'
propertyNoOptional property to return values for. Defaults vary by label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / label / description
      Previous value: -"The label to fetch values for"New value: +"The label to fetch values for (e.g., 'Brand', 'Location', 'Technology', 'Audience', 'RetailerType', 'Trend')"
    • addedInput schema / properties / property
      Added value: +{
+  "description": "Optional property to return values for. Defaults vary by label.",
+  "type": "string"
+}
    • 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",
-  "label",
-  "userId"
-]New value: +[
+  "graphId",
+  "label"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Number of values found",
-      "type": "number"
-    },
-    "label": {
-      "description": "The label queried",
-      "type": "string"
-    },
-    "values": {
-      "description": "Array of valid values for the label",
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv1.3.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is low; the description still adds meaningful behavior by noting that label="Trend" returns the full deterministic list whereas search may return partial results. It omits return shape and rate/pagination behavior, but the determinism disclosure is the key operational trait.

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?

Purpose and the Trend special case are front-loaded and the example queries earn their space, but the trailing parenthetical '(Graph taxonomy label value lookup.)' repeats information already stated in the first sentence.

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 only 4 parameters all fully documented in the schema, no output schema, and annotations covering safety, the description supplies enough context to call the tool correctly. Minor gaps remain around return format, which the absence of an output schema leaves unaddressed.

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 description coverage is 100%, so baseline is 3, but the description adds value beyond the schema by showing how the 'label' parameter selects the value set and by singling out label="Trend" as the deterministic full-list case, plus giving free-text example labels.

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 ('List all brands, locations, technologies, audiences, or trends within a specific knowledge graph') and clarifies it is a taxonomy value lookup, so an agent can distinguish it from search_graph and get_node without opening a schema.

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?

Gives clear triggering conditions with concrete example queries ('what brands are in the retail graph?') and a specific when-to-use case for label="Trend" where search may return partial results. It does not name the alternative sibling tools explicitly, but the alternative behavior (search) is described.

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