0xinsider

Get combo

get_combo

Read-onlyIdempotent

One Polymarket combo: legs, conjunction result, all-time trade totals, the newest 100 taker fills, lifecycle totals and ingest coverage. Requires a Pro or Max API key. Unlike get_combo_fills it keeps executions priced above 0.95. Null lifecycle or missing leg facts are unknown, never zero.

Args:

condition_id (string, required): Combo ID, 0x and 62 lowercase hex characters; not a binary market's condition_id

Returns: combo, fills, lifecycle, coverage, access and meta. A malformed ID is a bad_request error and an unknown one not_found.

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": {
      "condition_id": "<condition_id>"
    },
    "name": "get_combo"
  }
}

Input Schema

Name	Required	Description	Default
`condition_id`	Yes	Combo ID: 0x and 62 lowercase hex characters, not a binary market's condition_id

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- addedOutput schema / $defs / ResponseMeta / properties / continued_from_generation
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedNov 3, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "allOf": [
-      {
-        "$ref": "#/$defs/ComboDetail"
-      },
-      {
-        "properties": {
-          "meta": {
-            "$ref": "#/$defs/ResponseMeta"
-          }
-        },
-        "required": [
-          "meta"
-        ],
-        "type": "object"
-      }
-    ]
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "type": "string"
-          },
-          "doc_url": {
-            "type": "string"
-          },
-          "param": {
-            "type": "string"
-          },
-          "reason": {
-            "type": "string"
-          },
-          "request_id": {
-            "type": "string"
-          },
-          "retry_after_seconds": {
-            "minimum": 0,
-            "type": "integer"
-          },
-          "retry_at": {
-            "type": "string"
-          },
-          "status": {
-            "minimum": 0,
-            "type": "integer"
-          }
-        },
-        "required": [
-          "code"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "allOf": [
+      {
+        "$ref": "#/$defs/ComboDetail"
+      },
+      {
+        "properties": {
+          "meta": {
+            "$ref": "#/$defs/ResponseMeta"
+          }
+        },
+        "required": [
+          "meta"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "billing_url": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "doc_url": {
+            "type": "string"
+          },
+          "param": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          },
+          "request_id": {
+            "type": "string"
+          },
+          "retry_after_seconds": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "retry_at": {
+            "type": "string"
+          },
+          "status": {
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "code"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

AddedOct 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent read with a closed world, and the description adds material context beyond them: the tiered API-key requirement, the price>0.95 inclusion rule that differs from get_combo_fills, and error semantics (bad_request for malformed IDs, not_found for unknown). The 'null lifecycle or missing leg facts are unknown, never zero' note is a genuinely useful data-integrity warning that an agent could otherwise misread as zero volumes.

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?

The first sentence front-loads the payload contents, followed by the auth constraint, the sibling contrast, and the null-handling caveat in a logical order. The Args section duplicates the schema's condition_id description verbatim and could be dropped, which is the only meaningful waste.

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

Completeness5/5

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

For a single-resource read whose output schema already documents return shapes, the description supplies everything else an agent needs: access tier, an explicit deviation from the sibling's filtering, error cases, and sentinel-value semantics. Nothing required to call it correctly 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 coverage is 100% and the input schema already carries the pattern and the 'not a binary market's condition_id' disambiguation. The Args block in the description restates that same wording rather than adding format or lookup guidance, so this is the baseline case where the schema does the work.

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?

Names a specific verb and resource and enumerates exactly what the payload carries: legs, conjunction result, all-time trade totals, newest 100 taker fills, lifecycle totals and ingest coverage. It also differentiates itself from the sibling get_combo_fills by stating it keeps executions priced above 0.95, so an agent can choose between them without opening a 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?

Gives a clear precondition (requires a Pro or Max API key) and an explicit contrast with get_combo_fills, which is the closest alternative. It does not say when to prefer get_combos_summary over this tool for multi-combo or summary needs, so routing against that sibling is left to inference.

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

All 0xinsider 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.