Skip to main content
Glama
Sign In
Manifold Markets MCP Server

Manifold Markets MCP Server

by bmorphism
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

add_bounty

Add a bounty to a Manifold Markets prediction market to attract more accurate resolutions by offering additional mana rewards.

Instructions

Add bounty to a market

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contractId": "<contractId>",
      "amount": "<amount>"
    },
    "name": "add_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractIdYesMarket ID
amountYesAmount of mana to add as bounty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior1/5

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

No annotations provided, and description only states the action. No disclosure of side effects, idempotency, permissions, or success outcomes. A mutation tool with no behavioral context.

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?

Single sentence, front-loaded, no redundant words. Every word earns its place.

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?

For a simple tool with 2 params and no output schema, description is minimal. It lacks usage context and behavioral details, making it less helpful for an agent to decide when to invoke this tool versus siblings.

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%, so schema already documents both parameters. The description adds no extra meaning beyond what's in the schema. Baseline 3 applies.

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

Purpose5/5

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

The description 'Add bounty to a market' uses a specific verb 'add' and clear resource 'bounty' and 'market'. It distinguishes from siblings like 'award_bounty' (which likely assigns bounty to a user) and 'add_liquidity' (different resource).

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 on when to use vs. alternatives like award_bounty. No mention of prerequisites or context. Siblings exist but no differentiation provided.

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

Deploy Server

Other Tools