@alpha-arcade/mcp

merge_shares

Merge equal amounts of YES and NO outcome tokens from a prediction market to redeem USDC. Returns 1 USDC for each pair of YES and NO tokens.

Instructions

Merge equal YES and NO outcome tokens back into USDC. 1 YES + 1 NO = 1 USDC.

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": {
      "marketAppId": "<marketAppId>",
      "amount": "<amount>"
    },
    "name": "merge_shares"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes	Amount to merge in microunits
`marketAppId`	Yes	The market app ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.5Jul 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It only states the basic action, but does not disclose behavior for unequal amounts, fees, or whether the operation is destructive (tokens burned), leaving gaps for the agent.

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 extremely concise with one sentence and a formula, front-loading the core action without any unnecessary text.

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

Completeness3/5

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

Given no output schema, the description does not explain return values or prerequisites. It is adequate for a simple operation but lacks completeness for error conditions or required account state.

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% with both parameters described. The description adds no further semantic context beyond the schema, so 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 clearly states the action (merge equal YES and NO tokens) and the result (back into USDC with the formula 1 YES + 1 NO = 1 USDC), distinguishing it from siblings like split_shares.

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

Usage Guidelines3/5

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

The usage context is implied by the formula, but there is no explicit guidance on when to use this tool (e.g., closing positions) or when not to (e.g., if amounts are unequal), and no mention of alternatives.

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