Skip to main content
Glama
bmorphism

Manifold Markets MCP Server

get_market

Retrieve comprehensive details for any prediction market by providing its ID. Access market status, probabilities, and outcomes.

Instructions

Get detailed information about a specific market

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketIdYesMarket ID

Implementation Reference

  • Zod schema for get_market input validation: requires a 'marketId' string.
    const GetMarketSchema = z.object({
      marketId: z.string(),
    });
  • src/index.ts:228-237 (registration)
    Registration of the 'get_market' tool with its name, description, and input schema definition (marketId required).
      name: 'get_market',
      description: 'Get detailed information about a specific market',
      inputSchema: {
        type: 'object',
        properties: {
          marketId: { type: 'string', description: 'Market ID' },
        },
        required: ['marketId'],
      },
    },
  • Handler for 'get_market': parses marketId from args, calls Manifold API GET /v0/market/{marketId}, and returns the market details as JSON.
    case 'get_market': {
      const { marketId } = GetMarketSchema.parse(args);
      const response = await fetch(`${API_BASE}/v0/market/${marketId}`, {
        headers: { Accept: 'application/json' },
      });
    
      if (!response.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `Manifold API error: ${response.statusText}`
        );
      }
    
      const market = await response.json();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(market, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that the operation is read-only, safe, or idempotent. The phrase 'detailed information' implies a read, but lacks explicit safety guarantees or side-effect warnings.

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 (one short sentence), which is efficient. However, it is borderline under-specified given the complexity of the context (no annotations, many siblings). It earns its place but could use a bit more substance.

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?

The tool has no output schema and no annotations, yet the description only states that it 'gets detailed information'. It does not mention the return format, pagination, or any constraints (e.g., market must exist). For a simple retrieval tool, this is incomplete.

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 baseline is 3. The description adds 'detailed information' but does not elaborate on what 'detailed' entails beyond the schema's 'Market ID'. No additional syntax or format hints are given.

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 ('Get') and resource ('detailed information about a specific market'), which is adequate for a retrieval tool. However, it does not differentiate from sibling tools like 'search_markets' or 'get_positions', missing an opportunity to clarify scope.

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. Given the presence of 'search_markets' for listing and other tools, the description should explicitly state that this is for a single market by ID, but it fails to do so.

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