Skip to main content
Glama

Fodda Synthetic Expert Consult

by ai.fodda
OverviewDiscussionsAdmin

Server Details

Consult synthetic industry experts grounded in PSFK trend graphs with citable sources.

Glama couldn't complete the latest health check. 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
22.8% over 41 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
piers-fawkes/fodda-mcp
GitHub Stars
1
Server Listing
Fodda

TDQS

A4.3/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have clearly distinct purposes (search, node retrieval, graph listing, evidence lookup, etc.). The only potential confusion is between consult_analyst and consult_human_agent, which have nearly identical descriptions but differ in whether the expert is synthetic or human; still, the names and first lines disambiguate them.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., search_graph, list_analysts, request_deliverable, get_node). No mixed conventions or vague names like 'process' or 'helper', and the verbs match the action taken.

Tool Count5/5

14 tools is well within the ideal 3-15 range for a specialized consult server. Each tool serves a distinct role across discovery, consultation, graph exploration, visualization, and deliverable management with no redundancy or bloat.

Completeness5/5

The tool set covers the full workflow: discovering capabilities/graphs/analysts, consulting experts, searching and exploring knowledge graphs, retrieving evidence, generating visuals, requesting deliverables, and polling their status. No obvious dead ends or missing lifecycle steps for the stated purpose.

Tool Schema Changelog

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

  1. 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,focus?:boolean}], axes:{left,right,top,bottom}}. trend_constellation: {trends:[{name,x,y,focus?:boolean}], 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,focus?:boolean}], x_label?:string, y_label?:string}"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}"
  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 the chart data. Structure depends on chart_type. cultural_shifts: {shifts:[{from,to}]}. competitive_compass: {brands:[{name,x,y,focus?:boolean}], axes:{left,right,top,bottom}}. trend_constellation: {trends:[{name,x,y,focus?:boolean}], 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,focus?:boolean}], x_label?:string, y_label?:string}"

Related MCP Connectors

Related MCP Servers

  • ES Hub Signals MCP

    SydYuan
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to search and retrieve market signals, revenue ideas, and growth tactics from 2,000+ curated entries across 18 sources.
    -

  • anylens

    Slowper
    A
    license
    Not graded
    quality
    B
    maintenance
    Turn any link — video, PDF, screenshot, or article — into cached, timestamp-anchored understanding agents can query through lenses (explainer, build spec, teardown, design tokens, production blueprint). Every claim carries the exact second or page it came from.
    28 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources