Fodda Synthetic Expert Consult
Server Details
Consult synthetic industry experts grounded in PSFK trend 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.0% over 82 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
Scored across 17 tools
The descriptions work hard with explicit 'sibling routing' notes that separate consult_analyst (synthetic/classic/C-suite) from consult_human_agent (living practitioners), and find_expert (query search) from list_analysts (catalog browse). However, four sibling tools referenced as routing targets — search_statistics, search_insights, brand_tracker, verify_market_claim — are not present in the set, so an agent following the guidance will attempt calls that don't exist. The expert-discovery cluster (find_expert / list_analysts / get_capabilities) also overlaps enough to cause hesitation.
Every tool is snake_case and verb-first (get_, list_, search_, consult_, request_, verify_, find_, generate_, check_). The pattern is predictable and grouping is visible by prefix (get_/list_ = read, request_ = commission).
17 tools for a platform spanning knowledge graphs, expert consultation, deliverables, visualization, and account management is defensible, and each tool maps to a recognizable capability. A few peripheral tools (get_capabilities, get_my_account, get_label_values) edge it toward the heavy side.
The surface has real dead ends: search_statistics, search_insights, brand_tracker, and verify_market_claim are advertised internally as sibling tools but are absent, guaranteeing failed calls. Deliverables can be requested and polled but there is no way to list or cancel prior jobs, and account management is read-only (get_my_account with no credit or plan mutation).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
11 tool updates
- Changed
check_deliverable_status1 field changed- changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts."
- Changed
consult_analyst6 fields changed- changed
Input schema / properties / analyst_id / descriptionPrevious value: -"The internal expert ID of the Synthetic Analyst (e.g., 'brand-cmo' or from list_analysts). Never display raw IDs or slugs, internal field names, or tool names to the user — refer to the expert by display name."New value: +"The internal ID of the agent (from list_analysts or find_expert, e.g. 'brand-cmo', 'john-ruskin', or 'retail-synthetic'). This is an internal identifier; the agent's display name is in the response." - added
Input schema / properties / deepAdded value: +{ + "description": "Set true to have the agent conduct deep background research across specialist graphs and market data before answering (or detects 'do your homework' / 'deep breakdown' in multi-turn queries).", + "type": "boolean" +} - changed
Input schema / properties / query / descriptionPrevious value: -"The question or topic to discuss with the synthetic analyst"New value: +"The question or topic to discuss with the analyst" - changed
Input schema / properties / session_id / descriptionPrevious value: -"Pass the session_id from a previous consult response to continue that engagement — the analyst keeps context and follow-ups cost less. Omit for a one-off question."New value: +"Pass the session_id from a previous consult response to continue that engagement — the analyst keeps context across the session. Omit for a one-off question." - changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "coverage": { + "description": "Coverage tier: FULL, PARTIAL, or PENDING", + "type": "string" + }, + "credibility_anchor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Pedigree or executive role framing" + }, + "expert": { + "additionalProperties": {}, + "description": "Analyst information", + "properties": { + "analyst_id": { + "description": "Identifier of the analyst or persona", + "type": "string" + }, + "name": { + "description": "Display name of the analyst or persona", + "type": "string" + } + }, + "type": "object" + }, + "job_id": { + "description": "Job identifier if running asynchronous deep research", + "type": "string" + }, + "next_moves": { + "description": "Recommended next research or application actions" + }, + "sources_used": { + "description": "Sources, citations, and graph evidence cited in the analysis", + "items": {}, + "type": "array" + }, + "status": { + "description": "Status if running asynchronous deep research", + "type": "string" + } + }, + "type": "object" +}
- Changed
consult_human_agent5 fields changed- changed
Input schema / properties / analyst_id / descriptionPrevious value: -"The internal expert ID of the Human Agent (from list_analysts). Never display raw IDs or slugs, internal field names, or tool names to the user — refer to the expert by display name."New value: +"The expert ID of the Human Agent (from list_analysts or find_expert, e.g. 'ben-dietz-sic'). Refer to the expert by their display name and credentials in user-facing responses." - added
Input schema / properties / deepAdded value: +{ + "description": "Set true to have the human agent conduct deep background research across specialist graphs and market data before answering (or detects 'do your homework' / 'deep breakdown' in multi-turn queries).", + "type": "boolean" +} - changed
Input schema / properties / session_id / descriptionPrevious value: -"Pass the session_id from a previous consult response to continue that engagement — the human agent keeps context and follow-ups cost less. Omit for a one-off question."New value: +"Pass the session_id from a previous consult response to continue that engagement — the human agent keeps context across the session. Omit for a one-off question." - changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "coverage": { + "description": "Coverage tier: FULL, PARTIAL, or PENDING", + "type": "string" + }, + "credibility_anchor": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Official background credibility anchor of the Human Agent" + }, + "expert": { + "additionalProperties": {}, + "description": "Expert information", + "properties": { + "analyst_id": { + "description": "Identifier of the expert", + "type": "string" + }, + "name": { + "description": "Display name of the expert", + "type": "string" + } + }, + "type": "object" + }, + "job_id": { + "description": "Job identifier if running asynchronous deep research", + "type": "string" + }, + "next_moves": { + "description": "Recommended next research or application actions" + }, + "sources_used": { + "description": "Sources, citations, and graph evidence cited in the analysis", + "items": {}, + "type": "array" + }, + "status": { + "description": "Status if running asynchronous deep research", + "type": "string" + } + }, + "type": "object" +}
- Added
find_expert - Changed
get_capabilities2 fields changed- added
Input schema / properties / topicAdded 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" +} - changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts."
- Changed
get_label_values1 field changed- changed
Input schema / properties / label / descriptionPrevious 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."
- Changed
list_analysts3 fields changed- added
Input schema / properties / categoryAdded value: +{ + "description": "Filter by agent category: 'human_agent' (Human Agent), 'classic_agent' (Classic Agent), 'c_suite_agent' (C-Suite Agent), 'synthetic_agent' (Synthetic Agent), or 'all' (default).", + "enum": [ + "all", + "human_agent", + "classic_agent", + "c_suite_agent", + "synthetic_agent" + ], + "type": "string" +} - added
Input schema / properties / queryAdded value: +{ + "description": "Optional natural language search query to filter analysts by lane, domain, expertise, or topics (e.g. 'streetwear', 'earnings', 'marketing').", + "type": "string" +} - changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts."
- Changed
request_deliverable2 fields changed- changed
Input schema / properties / analyst_id / descriptionPrevious value: -"The internal analyst ID producing the deliverable (from list_analysts). Never display raw IDs or slugs, internal field names, or tool names to the user — refer to the expert by display name."New value: +"The internal analyst ID producing the deliverable (from list_analysts). This is an internal identifier; the expert's display name is in the response." - changed
Input schema / properties / userId / descriptionPrevious value: -"Optional user identifier."New value: +"Optional expert user identifier or email. Automatically resolved from authenticated API key for expert accounts."
- Added
request_expert_intro - Changed
search_graph3 fields changed- added
Input schema / properties / graphAdded value: +{ + "description": "Alias for graphId.", + "type": "string" +} - added
Input schema / properties / graph_idAdded value: +{ + "description": "Alias for graphId.", + "type": "string" +} - added
Input schema / properties / sectorAdded 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" +}
- Added
verify_claim
1 tool update
- Changed
generate_visual1 field changed- changed
Input schema / properties / data / descriptionPrevious 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}"
1 tool update
- Changed
generate_visual1 field changed- changed
Input schema / properties / data / descriptionPrevious 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
Brand health & trend footprint across PSFK expert graphs with citable sources, not web summaries.
Trend, stats & insight search across PSFK expert graphs with citable sources.
Autonomous deep research reports merging PSFK trend graphs with citable sources.
Synthetic audiences built from real people. Ask anyone anything before you decide.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides access to 9 AI executives offering board-ready business intelligence, competitor analysis, trend monitoring, and more via agent-payable endpoints.5MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to turn a rough brief into a sharp concept, brand idea, launch plan, or honest critique using a Frame → Make → Edit → Deliver method with 32 creative-direction principles. Each recommendation can be traced back to its underlying claims, paraphrased evidence notes, and public sources.10MIT
- AlicenseAqualityBmaintenanceLive trend data for your AI. 25+ platforms. One connection.346MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve market signals, revenue ideas, and growth tactics from 2,000+ curated entries across 18 sources.-
Glama MCP Gateway
Add one secure layer between your agents and this server.