Skip to main content
Glama
tanmay4l

Futarchy MCP Server

by tanmay4l

getProposals

Retrieve all governance proposals for a specific DAO to review active decisions and voting status.

Instructions

Get all proposals for a specific DAO

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daoIdYesThe ID of the DAO to get proposals for

Implementation Reference

  • The asynchronous handler function for the MCP 'getProposals' tool. It calls the FutarchyApiClient.getProposals method with the provided daoId, handles the response, and returns formatted text content or an error.
    async ({ daoId }) => {
      try {
        const response = await apiClient.getProposals(daoId);
        
        if (!response.success) {
          return {
            content: [
              {
                type: "text" as const,
                text: response.error || 'Unknown error',
              },
            ],
            isError: true,
          };
        }
        
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error fetching proposals: ${error.message || 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
  • Registration of the 'getProposals' MCP tool using McpServer.tool(), including the tool name, description, input schema (daoId), and handler reference.
    server.tool(
      "getProposals",
      "Get all proposals for a specific DAO",
      {
        daoId: z.string().describe("The ID of the DAO to get proposals for"),
      },
      async ({ daoId }) => {
        try {
          const response = await apiClient.getProposals(daoId);
          
          if (!response.success) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: response.error || 'Unknown error',
                },
              ],
              isError: true,
            };
          }
          
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error fetching proposals: ${error.message || 'Unknown error'}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema definition for the input parameters of getProposals (GetProposalsParamsSchema), matching the inline schema used in registration.
    export const GetProposalsParamsSchema = z.object({
      daoId: z.string().describe("The ID of the DAO to get proposals for"),
    });
  • Helper function in FutarchyApiClient that performs the actual HTTP fetch to retrieve proposals for a given DAO ID from the backend API.
    async getProposals(daoId: string): Promise<Response> {
      try {
        const response = await fetch(`${this.baseUrl}/daos/${daoId}/proposals`);
        if (!response.ok) {
          throw new Error(`HTTP error! Status: ${response.status}`);
        }
        const data = await response.json();
        
        return {
          success: true,
          data: data.proposals
        };
      } catch (error: any) {
        return {
          success: false,
          error: error.message || `Failed to fetch proposals for DAO: ${daoId}`
        };
      }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get all proposals') but does not describe key behaviors such as whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination, sorting), or potential rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is front-loaded with the core purpose ('Get all proposals for a specific DAO'), making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a tool that retrieves multiple proposals, the lack of annotations and output schema means the description is incomplete. It does not cover behavioral aspects like response format, error handling, or usage context, which are crucial for an agent to use the tool effectively in a real-world scenario.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'daoId' parameter clearly documented. The description adds no additional meaning beyond what the schema provides, such as explaining what a DAO ID format looks like or providing examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('all proposals for a specific DAO'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'getProposal' (singular) or 'getDaos', which reduces specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not clarify if this should be used for listing proposals versus retrieving a single proposal with 'getProposal', or when to use it in relation to other DAO-related tools like 'getDao' or 'getDaos'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tanmay4l/FutarchyMCPServer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server