Skip to main content
Glama
bmorphism

Manifold Markets MCP Server

unresolve_market

Change a resolved prediction market back to an unresolved state. Useful for correcting errors or reopening markets.

Instructions

Unresolve a previously resolved market

Input Schema

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

Implementation Reference

  • Zod schema for unresolve_market input validation: requires contractId, optional answerId for multiple choice markets
    const UnresolveMarketSchema = z.object({
      contractId: z.string(),
      answerId: z.string().optional(),
    });
  • src/index.ts:313-324 (registration)
    Tool registration in the list of tools with name 'unresolve_market', description, input schema definition
    {
      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']
      }
    },
  • Handler for unresolve_market: parses params via Zod schema, checks API key, POSTs to /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',
          },
        ],
      };
Behavior2/5

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

With no annotations, the description must carry the behavioral burden. It only states 'Unresolve' without explaining side effects, permissions, or reversibility. This is insufficient for a potentially destructive mutation.

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

Conciseness4/5

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

The description is extremely concise at two words, with no wasted text. However, it lacks structure (e.g., bullet points or line breaks) but still effectively communicates the core action.

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 no annotations, no output schema, and only two parameters, the description is too minimal. It fails to explain what happens when unresolved, any conditions, or side effects, leaving the agent with gaps.

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 coverage is 100%, so the input schema already documents the parameters. The description adds no extra meaning beyond what is in the schema, so baseline score 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 'Unresolve' and the resource 'market', indicating the action is reverting a previous resolution. It is distinct from siblings like close_market or create_market, though it doesn't explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites (e.g., the market must be resolved). The agent must infer context from the tool name.

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