Fodda Context Layer

search_graph

Read-only

Research market trends, category dynamics, and competitor intelligence across 100+ curated knowledge graphs. Returns cited evidence, lifecycle stages, and structured next_moves for investigation.

Instructions

Use when researching market trends, category dynamics, consumer behavior shifts, competitor intelligence, or broad topic investigation across 100+ curated knowledge graphs. Returns trends with cited evidence, lifecycle stage (emerging/building/mature), and structured next_moves. If query names a company/brand, prefer brand_tracker.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Execution mode: "research" for topic research, "compare" for upload & compare intelligence. Defaults to "research".	research
`graph`	No	Alias for graphId.
`limit`	No	Maximum number of results (default 10, max 50)
`query`	Yes	The search query. Country/regional terms filter results at the macro level. Note: Knowledge graph trends are indexed at country/global scope — for sub-national or city-level data (e.g., "US coastal cities"), also query get_supplemental_context.
`graphs`	No	Optional explicit graph scope: an array of graph IDs. When provided, the search is restricted to EXACTLY these graphs — no fallback routing to other graphs. Graph IDs that are unknown, not live, or not yet synced are reported back in `unavailable_graphs` with a reason. Takes precedence over graphId.
`sector`	No	Optional sector focus (e.g. 'Alcoholic Drinks', 'Non-Alcoholic Drinks', 'Food & Beverage', 'Retail', 'Beauty', 'Sports', 'Technology', 'Luxury Goods'). When provided, scopes trend discovery to this sector.
`userId`	No	Optional user identifier for trial usage tracking.
`graphId`	No	Optional graph ID. If omitted, searches ALL accessible graphs. 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', 'delta/the-connection-index'
`graph_id`	No	Alias for graphId.
`skip_skills`	No	If true, skip applying any enabled search enhancement skills for this query only. Use when you want raw, un-enhanced graph results. Default: false.
`use_semantic`	No	Whether to use semantic search (default true)
`include_evidence`	No	If true, batch-fetch supporting evidence articles inline with results. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv1.3.3Oct 7, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / graph

Added value: +{
+  "description": "Alias for graphId.",
+  "type": "string"
+}

changedInput schema / properties / graphId / description

Previous value: -"The graph ID. For PSFK verticals use: 'retail', 'beauty', or 'sports'. Other graphs: 'psfk' (all verticals), 'sic' (Strategic Independent Culture), 'waldo'."New value: +"Optional graph ID. If omitted, searches ALL accessible graphs. 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', 'delta/the-connection-index'"

addedInput schema / properties / graph_id

Added value: +{
+  "description": "Alias for graphId.",
+  "type": "string"
+}

addedInput schema / properties / graphs

Added value: +{
+  "description": "Optional explicit graph scope: an array of graph IDs. When provided, the search is restricted to EXACTLY these graphs — no fallback routing to other graphs. Graph IDs that are unknown, not live, or not yet synced are reported back in `unavailable_graphs` with a reason. Takes precedence over graphId.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / include_evidence

Added value: +{
+  "description": "If true, batch-fetch supporting evidence articles inline with results. Default: true.",
+  "type": "boolean"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results (default 25, max 50)"New value: +"Maximum number of results (default 10, max 50)"

addedInput schema / properties / mode

Added value: +{
+  "default": "research",
+  "description": "Execution mode: \"research\" for topic research, \"compare\" for upload & compare intelligence. Defaults to \"research\".",
+  "enum": [
+    "research",
+    "compare"
+  ],
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"The search query"New value: +"The search query. Country/regional terms filter results at the macro level. Note: Knowledge graph trends are indexed at country/global scope — for sub-national or city-level data (e.g., \"US coastal cities\"), also query get_supplemental_context."

addedInput schema / properties / sector

Added value: +{
+  "description": "Optional sector focus (e.g. 'Alcoholic Drinks', 'Non-Alcoholic Drinks', 'Food & Beverage', 'Retail', 'Beauty', 'Sports', 'Technology', 'Luxury Goods'). When provided, scopes trend discovery to this sector.",
+  "type": "string"
+}

addedInput schema / properties / skip_skills

Added value: +{
+  "description": "If true, skip applying any enabled search enhancement skills for this query only. Use when you want raw, un-enhanced graph results. Default: false.",
+  "type": "boolean"
+}

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",
-  "query",
-  "userId"
-]New value: +[
+  "query"
+]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "results": {
-      "description": "Array of matching nodes (trends, articles)",
-      "type": "array"
-    },
-    "search_method": {
-      "description": "Search method used: 'vector', 'keyword', or 'fallback'",
-      "type": "string"
-    },
-    "total": {
-      "description": "Total number of results found",
-      "type": "number"
-    },
-    "usage": {
-      "description": "Billing/usage metadata",
-      "properties": {
-        "total_billable_units": {
-          "type": "number"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null

First observedv1.3.2Feb 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds real behavioral context beyond them: it discloses the return shape (trends + cited evidence + lifecycle stage + next_moves) and cross-graph reachability (100+ graphs). It does not explain the idempotentHint=false nuance or result limits beyond 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 tight sentences: usage first, then return contract, then sibling routing. 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.

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 correctly compensates by summarizing the return payload. For a 12-parameter tool it leaves the multi-alias scoping (graph vs graphId vs graphs) and mode=compare semantics to the schema, which is reasonable, but it could say more about graph selection behavior.

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 (mode, graphs, graphId alias, sector, limit, use_semantic, include_evidence, etc.) is already documented in the schema. The description adds no parameter-level detail such as mode semantics or graph-scoping precedence, so 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 (search across 100+ curated knowledge graphs) plus the output contract (trends with cited evidence, lifecycle stage, next_moves). It also names the sibling to use instead for company/brand queries, so an agent can discriminate without opening 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?

Explicit when-to-use list (market trends, category dynamics, consumer behavior shifts, competitor intelligence, broad topic investigation) and an explicit routing rule: prefer brand_tracker when the query names a company/brand. The alternatives condition is stated, not implied.

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

Deploy Server

search_graph

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools