Skip to main content
Glama

Quote a prediction trade

quote_prediction_trade
Read-only

Exact quote from the market maker: shares for a USDC buy, or USDC for a share sell, fees included.

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": {
      "id": "<id>",
      "side": "<side>",
      "action": "<action>",
      "amount": "<amount>"
    },
    "name": "quote_prediction_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesprediction market id
sideYes
actionYes
amountYesUSDC to spend (buy) or shares to sell (sell), as a decimal string, e.g. "25" or "0.5"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds genuine context beyond that — the price originates from a market maker and already includes fees — but says nothing about quote freshness, expiry, slippage assumptions, or whether the figure is guaranteed at execution time.

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?

One dense sentence with the key concept (exact market-maker quote) front-loaded and the buy/sell asymmetry packed into the same clause. Nothing is wasted, though the fragment after the colon reads slightly tersely.

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?

With no output schema, the description must carry the burden of describing the return, and it only says "shares ... or USDC ... fees included" — no indication of whether a quote id, expiry, or price impact is returned. For a four-parameter, all-required pricing tool this is adequate but leaves real 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 50%: id and amount are documented, while the side and action enums carry no descriptions. The description compensates partly by explaining that amount means shares on a buy and shares on a... more precisely that a buy consumes USDC for shares and a sell converts shares to USDC, which clarifies the unit of amount in each direction.

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?

"Exact quote from the market maker" names a specific verb (quote) and resource (prediction trade), and the buy/sell restatement pins down what is being priced. It does not name the sibling build_prediction_trade, so the boundary between quoting and building an order is left implicit.

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?

There is no explicit when-to-use statement, no prerequisite, and no named alternative. An agent must infer from the word "quote" that this is a read-only price check that precedes build_prediction_trade rather than a substitute for it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources