Skip to main content
Glama

Fodda Brand Intelligence

by ai.fodda
OverviewDiscussionsAdmin

Server Details

Brand health & trend footprint across PSFK expert graphs with citable sources, not web summaries.

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.5% 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 13 tools

Disambiguation4/5

Most tools have clearly separated roles—searching, node lookups, evidence retrieval, supplemental data, and visualization—so an agent can generally pick the right one. The main friction is brand_tracker versus search_graph, since both describe all-graph brand and competitive intelligence searches; descriptions help but the boundary is not perfectly crisp.

Naming Consistency4/5

The naming is predominantly snake_case verb_object, with a strong get_ prefix for retrieval operations and other action verbs like search_, list_, generate_, check_, and read_. Minor deviations such as brand_tracker (a noun-style name) and check_supplemental_status vs. get_supplemental_context keep it from being fully consistent.

Tool Count5/5

At 13 tools, the server sits well within the ideal 3–15 range, and each tool maps to a distinct capability: graph discovery, label enumeration, search, node/neighbor/evidence lookups, brand aggregation, supplemental market data, visualization, and account/URL utilities. The count feels well-scoped for a brand-intelligence platform rather than padded or thin.

Completeness4/5

The read-only research lifecycle is well covered: list accessible graphs, enumerate labels, search trends, retrieve node/neighbor/evidence details, build brand profiles, gather supplemental market data, and generate visuals. Minor gaps exist—such as no dedicated tool for directly cross-referencing an extracted URL against graphs and no explicit brand-to-brand comparison—but agents can work around these using search_graph and related tools.

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

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