Skip to main content
Glama
bmorphism

Manifold Markets MCP Server

unresolve_market

Reopens a resolved prediction market on Manifold Markets to allow further trading and updates to market outcomes.

Instructions

Unresolve a previously resolved market

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractIdYesMarket ID
answerIdNoOptional. Answer ID for multiple choice markets

Implementation Reference

  • Executes the unresolve_market tool: parses params with UnresolveMarketSchema, requires MANIFOLD_API_KEY, POSTs to Manifold /v0/unresolve endpoint, returns success message.
    case 'unresolve_market': {
      const params = UnresolveMarketSchema.parse(args);
      const apiKey = process.env.MANIFOLD_API_KEY;
      if (!apiKey) {
        throw new McpError(
          ErrorCode.InternalError,
          'MANIFOLD_API_KEY environment variable is required'
        );
      }
    
      const response = await fetch(`${API_BASE}/v0/unresolve`, {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json',
          Authorization: `Key ${apiKey}`,
        },
        body: JSON.stringify(params),
      });
    
      if (!response.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `Manifold API error: ${response.statusText}`
        );
      }
    
      return {
        content: [
          {
            type: 'text',
            text: 'Market unresolved successfully',
          },
        ],
      };
    }
  • Zod schema defining input for unresolve_market: contractId (string, required), answerId (string, optional).
    const UnresolveMarketSchema = z.object({
      contractId: z.string(),
      answerId: z.string().optional(),
    });
  • src/index.ts:313-324 (registration)
    Registers the unresolve_market tool in the ListTools response with name, description, and input schema.
    {
      name: 'unresolve_market',
      description: 'Unresolve a previously resolved market',
      inputSchema: {
        type: 'object',
        properties: {
          contractId: { type: 'string', description: 'Market ID' },
          answerId: { type: 'string', description: 'Optional. Answer ID for multiple choice markets' }
        },
        required: ['contractId']
      }
    },
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. While 'unresolve' implies a mutation that changes a market's state, the description doesn't clarify permissions needed, whether this action is reversible, potential side effects, or what the response looks like. This leaves significant gaps for a tool that likely modifies data.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 lack of annotations and output schema, the description is insufficient for a mutation tool. It doesn't explain what 'unresolving' entails operationally, the expected outcome, or error conditions, leaving the agent with incomplete context for safe and effective use.

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?

Schema description coverage is 100%, with clear parameter documentation in the input schema. The description doesn't add any semantic details beyond what the schema provides, such as explaining the relationship between 'contractId' and 'answerId' or providing examples. This meets the baseline for high schema coverage.

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 action ('unresolve') and the resource ('a previously resolved market'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'close_market' or 'create_market' by explaining what 'unresolving' specifically entails in this context versus those other market operations.

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. It doesn't specify prerequisites (e.g., that the market must already be resolved), exclusions, or compare it to sibling tools like 'close_market' or 'create_market' for context on appropriate usage scenarios.

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/bmorphism/manifold-mcp-server'

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