Gogi

Execute Prediction Order

execute_prediction

Destructive

Place a potentially money-moving prediction-market order on Kalshi or Polymarket. Call search_predictions first to identify the current contract, then verify the connected account, side, contracts, and price. This action may be irreversible; policy and in-app confirmation still apply when enabled.

Input Schema

TableJSON Schema

Name	Required	Description
`side`	Yes	Contract outcome or order direction.
`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)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds genuine value by flagging that the action 'may be irreversible' and that policy and in-app confirmation still apply when enabled, which is not derivable from the annotations.

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 tight sentences, front-loaded with the action and venue, followed by the prerequisite step and the irreversibility caveat. No filler; each sentence carries distinct information.

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?

For a destructive, non-idempotent mutation tool, the description covers prerequisites, venue scope, and irreversibility, and an output schema exists so return values need not be explained. Only a clearer statement of what confirmation/policy entails is missing.

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 side, ticker, platform, contracts, and price_cents are already documented with types, enums, and ranges. The description references verifying account, side, contracts, and price but adds no format or constraint detail 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?

States a specific verb (place) and resource (prediction-market order) with explicit venue scope (Kalshi or Polymarket). The 'prediction-market' qualifier cleanly separates it from the generic execute_trade sibling without needing to open either schema.

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?

Explicitly routes the agent to search_predictions first to identify the current contract, which is a concrete usage precondition. It also lists what to verify before executing. It stops short of naming when NOT to use this or contrasting directly with execute_trade, so not a full 5.

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?