Fodda
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | SSE server port (omit for stdio mode) | |
| NODE_ENV | No | Environment (development / production) | production |
| FODDA_API_URL | No | Upstream API base URL | https://api.fodda.ai |
| RATE_LIMIT_RPM | No | Requests per minute per API key | 60 |
| FODDA_MCP_SECRET | No | HMAC signing secret | |
| INTERNAL_TEST_KEYS | No | Comma-separated keys for simulation mode |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_graphA | Perform hybrid (vector + keyword) search on a Fodda knowledge graph. Returns trends and articles matching the query. Uses a 3-tier fallback: vector search → keyword search → all trends. Always returns results. |
| get_neighborsB | Traverse the graph from seed nodes to find related concepts and relationships. Useful for depth-first discovery. |
| get_evidenceC | Get source signals, articles, and evidentiary depth for a specific node. Essential for provenance and fact-checking. |
| get_nodeB | Directly retrieve metadata and properties for a single node by its ID. |
| get_label_valuesA | Discover valid values for a specific node label (e.g., RetailerType, Technology). Use for discovery, UI filters, and category exploration. |
| psfk_overviewA | Get a structured macro overview from the PSFK Graph. Returns up to 3 meta_patterns. Useful for top-level briefings before deeper exploration. At least one of 'industry' or 'sector' must be provided. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: get_evidence focuses on source signals and provenance, get_label_values on label discovery, get_neighbors on graph traversal, get_node on direct metadata retrieval, psfk_overview on macro patterns, and search_graph on hybrid search. The descriptions reinforce these unique roles, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_evidence, get_label_values, get_neighbors, get_node, search_graph). The only deviation is psfk_overview, which still maintains a noun_noun structure that fits the pattern without mixing conventions, ensuring predictability and readability.
With 6 tools, this server is well-scoped for graph exploration and knowledge retrieval. Each tool serves a specific function in the workflow (e.g., discovery, traversal, search, metadata access), and none appear redundant or excessive, making the count appropriate for the domain.
The tool set covers core operations for graph-based knowledge exploration: retrieval (get_node, get_evidence), traversal (get_neighbors), search (search_graph), discovery (get_label_values), and overview (psfk_overview). A minor gap exists in update or manipulation tools (e.g., add_node, modify_relationships), but agents can likely work around this for read-only analysis.