Skip to main content
Glama

Fodda Deep Research

Server Details

Autonomous deep research reports merging 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.4% 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.2/5.0

Scored across 14 tools

Disambiguation4/5

Most tools target clearly distinct steps: graph discovery, search, node/evidence/neighbor retrieval, and status polling. Mild overlap exists between deep_research_topic and get_supplemental_context, and between search_graph and get_label_values, but the descriptions provide explicit usage rules to resolve ambiguity.

Naming Consistency4/5

The vast majority of tools follow a clear verb_noun snake_case pattern: get_node, search_graph, list_graphs, check_research_status. The one clear deviation is deep_research_topic, which reads more like a noun phrase than an imperative action, but it is still readable and consistent in style.

Tool Count5/5

Fourteen tools is well within the ideal range for a research platform of this scope. Each tool earns its place by covering a distinct step in the workflow from graph discovery and deep dives to supplemental data, visualization, and account/capability checks.

Completeness5/5

The tool set covers the full research lifecycle: discover graphs, search trends, retrieve detailed nodes/evidence/neighbors, launch deep or supplemental research with status polling, ingest external URLs, and generate visuals. There are no obvious dead ends for the intended read-only research use case.

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}], 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.