Futarchy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getDaosB | Get all DAOs from the Futarchy system |
| getDaoC | Get a specific DAO by ID |
| getProposalsC | Get all proposals for a specific DAO |
| getProposalC | Get a specific proposal by ID |
| createProposalC | Create a new proposal for a DAO |
| getProposalSentimentC | Get sentiment analysis for a specific proposal based on Discord and Twitter data |
| buyInPassMarketC | Buy tokens in the pass market for a proposal |
| sellInPassMarketC | Sell tokens in the pass market for a proposal |
| buyInFailMarketC | Buy tokens in the fail market for a proposal |
| sellInFailMarketC | Sell tokens in the fail market for a proposal |
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 10 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are clearly separated into DAO operations (getDao, getDaos), proposal operations (createProposal, getProposal, getProposals), market operations (buy/sell in pass/fail markets), and sentiment analysis (getProposalSentiment). The descriptions make it immediately clear which tool to use for each specific action.
All tools follow a consistent verb_noun pattern throughout. The naming convention is perfectly uniform with clear action prefixes (buyIn, sellIn, create, get) followed by specific objects (FailMarket, PassMarket, Proposal, Dao, ProposalSentiment). There are no deviations in style or convention across the entire toolset.
With 10 tools, this is well-scoped for a Futarchy system. Each tool earns its place by covering distinct aspects of the domain: DAO management, proposal lifecycle, market trading operations, and sentiment analysis. The count is appropriate for the apparent scope without being overwhelming or insufficient.
The tool surface provides complete CRUD/lifecycle coverage for the Futarchy domain. It covers DAO discovery (getDaos, getDao), proposal creation and retrieval (createProposal, getProposal, getProposals), market operations for both pass and fail outcomes (buy/sell), and even sentiment analysis. There are no obvious gaps or dead ends for agents working with this system.