Skip to main content
Glama

Fodda Topic & Trend Research

Server Details

Trend, stats & insight search across PSFK expert graphs with citable sources.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
12.6% over 81 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
piers-fawkes/fodda-mcp
GitHub Stars
1
Server Listing
Fodda Context Layer
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 15 tools

Disambiguation4/5

Most tools target clearly distinct resources: graph search, node metadata, neighbor traversal, evidence lookup, taxonomy values, live macro feeds, account status, and visualization. The only real ambiguity is the search_graph / search_statistics / search_insights triad, which all query the same knowledge graphs and differ only by content layer, but the descriptions explicitly route between them and even warn against misusing get_label_values for topic search.

Naming Consistency5/5

Every name is a consistent snake_case verb_noun pair (get_node, search_graph, list_graphs, generate_visual, check_supplemental_status), with no camelCase or bare-noun exceptions. Verb choice is predictable: get_ for single-object retrieval, search_ for query layers, list_ for catalogs.

Tool Count4/5

15 tools is at the top of the reasonable band but each maps to a genuine capability layer (discovery, three retrieval layers, graph traversal, external data, account, viz). Slightly heavy — the three sibling search tools plus a polling status tool pad the surface, but nothing is clearly dead weight.

Completeness3/5

Core research lifecycle is covered well: discover graphs, search trends, drill into nodes, pull evidence, bolt on live government data, and render a chart. However, the routing text references two tools that are absent from the set — consult_human_agent and brand_tracker — creating dead ends an agent will hit when following the stated sibling routing, and there is no report/export or agent-interaction capability to close the workflow.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 6 tool updates
    • Changedget_capabilities2 fields changed
      • addedInput schema / properties / topic
        Added value: +{
        +  "description": "Optional subject, brand, category, or problem statement to assess topic reconnaissance ('What does Fodda know about [topic]?'). If omitted, returns platform capability overview, workflow recipes, and specialist breakdown.",
        +  "type": "string"
        +}
      • changedInput schema / properties / userId / description
        Previous value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts."
    • Changedget_label_values1 field changed
      • changedInput schema / properties / label / description
        Previous value: -"The label to fetch values for (e.g., 'Brand', 'Location', 'Technology', 'Audience', 'RetailerType', 'Trend')"New value: +"The label to fetch values for (e.g., 'Brand', 'Location', 'Technology', 'Audience', 'RetailerType', 'Trend'). Note: caps at 100 values alphabetically."
    • Changedget_supplemental_context1 field changed
      • changedInput schema / properties / query / description
        Previous value: -"The topic or query to get supplemental data for (e.g., 'sustainable packaging', 'tequila spirits market', 'Gen Z beauty'). Include country names if searching non-US markets (e.g. 'Thailand consumer sentiment')."New value: +"The topic or query to get supplemental data for (e.g., 'US retail sales', 'consumer spending', 'sustainable packaging', 'Gen Z beauty'). Include country names if searching non-US markets (e.g. 'Thailand consumer sentiment'). When querying retail sales or consumer spending, returns official Headline Retail & Food Services (RSAFS, ~\\$738B) vs Ex-Food (RSXFS, ~\\$646B) and live Monthly PCE (Table T20805, ~\\$22.3T)."
    • Changedsearch_graph3 fields changed
      • addedInput schema / properties / graph
        Added value: +{
        +  "description": "Alias for graphId.",
        +  "type": "string"
        +}
      • addedInput schema / properties / graph_id
        Added value: +{
        +  "description": "Alias for graphId.",
        +  "type": "string"
        +}
      • 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"
        +}
    • Changedsearch_insights3 fields changed
      • changedInput schema / properties / graph_id / description
        Previous value: -"Graph ID to search. Works on ALL graphs — domain graphs ('retail', 'sic', 'beauty', 'sports', 'fashion', 'ce-design', 'pew') AND expert graphs. Search across multiple graphs for best coverage."New value: +"Optional graph ID to search. If omitted (or when sector is provided), searches across all relevant graphs in parallel. Examples: 'food', 'retail', 'tech', 'travel', 'beauty', 'sports', 'fashion', 'sic', 'pew', 'ce-design'."
      • addedInput schema / properties / sector
        Added value: +{
        +  "description": "Optional sector focus to filter results (e.g. 'Alcoholic Drinks', 'Non-Alcoholic Drinks', 'Food & Beverage', 'Retail', 'Beauty', 'Sports', 'Technology', 'Luxury Goods'). When provided, bypasses graph IDs and scopes insights extraction to this sector across graphs.",
        +  "type": "string"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "graph_id",
        -  "query"
        -]New value: +[
        +  "query"
        +]
    • Changedsearch_statistics3 fields changed
      • changedInput schema / properties / graph_id / description
        Previous value: -"Graph ID to search. Works on ALL graphs — domain graphs ('retail', 'fashion', 'beauty', 'sports', 'sic', 'ce-design', 'pew') AND expert graphs. Search across multiple graphs for best coverage."New value: +"Optional graph ID to search. If omitted (or when sector is provided), searches across all relevant graphs in parallel. Examples: 'food', 'retail', 'tech', 'travel', 'fashion', 'beauty', 'sports', 'sic', 'pew', 'ce-design'."
      • addedInput schema / properties / sector
        Added value: +{
        +  "description": "Optional sector focus to filter results (e.g. 'Alcoholic Drinks', 'Non-Alcoholic Drinks', 'Food & Beverage', 'Retail', 'Beauty', 'Sports', 'Technology', 'Luxury Goods'). When provided, bypasses graph IDs and scopes evidence extraction to this sector across graphs.",
        +  "type": "string"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "graph_id",
        -  "query"
        -]New value: +[
        +  "query"
        +]
  2. 1 tool update
    • Changedgenerate_visual1 field changed
      • changedInput schema / properties / data / description
        Previous value: -"JSON string containing the chart data. Structure depends on chart_type. cultural_shifts: {shifts:[{from,to}]}. competitive_compass: {brands:[{name,x,y}], axes:{left,right,top,bottom}}. trend_constellation: {trends:[{name,x,y}], connections:[{from,to,strength}]}. implication_ladder: {signal,trend,so_what,do_what}. innovation_pathway: {now,near_term,future}. opportunity_map: {items:[{name,consumer_desire,market_activity}]}"New value: +"JSON string containing chart data. Optional top-level \"focus\":\"Name\" or per-item \"focus\":true highlights key entity in brand accent. cultural_shifts: {shifts:[{from,to}]}. competitive_compass: {brands:[{name,x,y,focus?:boolean}], axes:{left,right,top,bottom}, focus?:string}. trend_constellation: {trends:[{name,x,y,focus?:boolean}], connections:[{from,to,strength}], focus?:string}. implication_ladder: {signal,trend,so_what,do_what}. innovation_pathway: {now,near_term,future}. opportunity_map: {items:[{name,consumer_desire,market_activity,focus?:boolean}], x_label?:string, y_label?:string, focus?:string}"

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.