Gogi

Execute Prediction Order

execute_prediction

Destructive

Money-moving Kalshi/Polymarket order (may be irreversible). Policy and in-app confirmation still apply when enabled. Use search_predictions to find contracts when the ticker is unknown.

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": {
      "ticker": "<ticker>",
      "side": "<side>",
      "contracts": "<contracts>"
    },
    "name": "execute_prediction"
  }
}

Input Schema

Name	Required	Description
`side`	Yes	Kalshi: the outcome to buy, 'yes' or 'no'. Polymarket: 'buy' or 'sell' the outcome token given as ticker.
`ticker`	Yes	Prediction-market contract ticker.
`platform`	No	Prediction-market venue for the connected account.
`contracts`	Yes	Positive number of contracts to purchase or sell.
`price_cents`	No	Limit price in cents (1-99)
`broker_account_id`	No	Optional Connections-enabled account_ref from list_brokers; defaults to the first enabled account on the venue.

Output Schema

Name	Required	Description	Default
`error`	No
`message`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / side / description

Previous value: -"Contract outcome or order direction."New value: +"Kalshi: the outcome to buy, 'yes' or 'no'. Polymarket: 'buy' or 'sell' the outcome token given as ticker."

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / broker_account_id / description

Previous value: -"Optional Connections-enabled account id from list_brokers; defaults to the first enabled account on the venue."New value: +"Optional Connections-enabled account_ref from list_brokers; defaults to the first enabled account on the venue."

changedInput schema / properties / broker_account_id / type
```
Previous value: -"integer"New value: +"string"
```

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / broker_account_id

Added value: +{
+  "description": "Optional Connections-enabled account id from list_brokers; defaults to the first enabled account on the venue.",
+  "type": "integer"
+}

Changed3 schema fields changedSep 13, 2026

addedInput schema / properties / platform / description

Added value: +"Prediction-market venue for the connected account."

changedOutput schema / description

Previous value: -"Structured Gogi result. Error responses include error and message fields."New value: +"Structured result. Error responses include error and message."

addedOutput schema / properties

Added value: +{
+  "error": {
+    "type": "string"
+  },
+  "message": {
+    "type": "string"
+  },
+  "success": {
+    "type": "boolean"
+  }
+}

Changed4 schema fields changedSep 13, 2026

addedInput schema / properties / contracts / description

Added value: +"Positive number of contracts to purchase or sell."

addedInput schema / properties / side / description

Added value: +"Contract outcome or order direction."

changedInput schema / properties / ticker / description

Previous value: -"Contract ticker"New value: +"Prediction-market contract ticker."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured Gogi result. Error responses include error and message fields.",
+  "type": "object"
+}

First observedSep 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely new context beyond that: 'may be irreversible' plus the note that policy and in-app confirmation still apply when enabled, telling the agent a call can be gated or rejected downstream. It does not cover rejection/partial-fill behavior or whether an omitted price becomes a market order.

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?

Three short clauses, zero filler: the destructive nature is front-loaded, then the confirmation caveat, then the discovery alternative. Every sentence carries information an agent needs before invoking a money-moving tool.

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

Completeness4/5

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

An output schema exists and annotations cover the safety flags, so the description only needs to supply intent, risk, and routing — all of which are present. The remaining minor gap is what happens when optional fields like price_cents or platform are omitted, but that is largely implied by the schema defaults.

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 every parameter including the side enum semantics, price_cents range, and broker_account_id default is already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 opening phrase 'Money-moving Kalshi/Polymarket order' names both the verb (executing an order) and the specific resource/venue, so an agent can distinguish it from search_predictions and from the generic execute_trade sibling. It stops short of explicitly contrasting with execute_trade, so it is clear but not fully sibling-differentiated.

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

Usage Guidelines4/5

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

It gives a concrete routing rule: use search_predictions when the ticker is unknown, which is exactly the decision point an agent faces before calling this tool. It does not state when NOT to use it (e.g., versus execute_trade for non-prediction-market assets), so the exclusion half of the guidance is missing.

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

All Gogi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?