Crypto Bot Audit + Market Data (x402 paid)

Polymarket market detail

market_poly_market_detail

Read-onlyIdempotent

Everything Polymarket's API records for one market id: the question and description, resolution source and resolver, outcomes and prices, the whole volume and liquidity series it reports, fees and the CLOB token ids. Costs $0.001 USDC per call. Byte-identical to GET /market/poly-market-detail?id=559681.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Polymarket numeric market id [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`ts`	No
`note`	No
`slug`	No
`found`	No
`stale`	No
`active`	No
`caveat`	No
`closed`	No
`reason`	No
`source`	No
`spread`	No
`bestAsk`	No
`bestBid`	No
`endDate`	No
`feeType`	No
`umaBond`	No
`outcomes`	No
`question`	No
`startDate`	No
`umaReward`	No
`volumeNum`	No
`resolvedBy`	No
`volume24hr`	No
`conditionId`	No
`description`	No
`clobTokenIds`	No
`liquidityNum`	No
`makerBaseFee`	No
`orderMinSize`	No
`takerBaseFee`	No
`outcomePrices`	No
`lastTradePrice`	No
`acceptingOrders`	No
`enableOrderBook`	No
`resolutionSource`	No
`oneDayPriceChange`	No
`resolutionStatuses`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "acceptingOrders": {
+      "type": "boolean"
+    },
+    "active": {
+      "type": "boolean"
+    },
+    "bestAsk": {
+      "type": "number"
+    },
+    "bestBid": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clobTokenIds": {
+      "items": {},
+      "type": "array"
+    },
+    "closed": {
+      "type": "boolean"
+    },
+    "conditionId": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "enableOrderBook": {
+      "type": "boolean"
+    },
+    "endDate": {
+      "type": "string"
+    },
+    "feeType": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "lastTradePrice": {
+      "type": "number"
+    },
+    "liquidityNum": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "makerBaseFee": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "oneDayPriceChange": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "orderMinSize": {
+      "type": "integer"
+    },
+    "outcomePrices": {
+      "items": {},
+      "type": "array"
+    },
+    "outcomes": {
+      "items": {},
+      "type": "array"
+    },
+    "question": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolutionSource": {
+      "type": "string"
+    },
+    "resolutionStatuses": {
+      "items": {},
+      "type": "array"
+    },
+    "resolvedBy": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "spread": {
+      "type": "number"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "startDate": {
+      "type": "string"
+    },
+    "takerBaseFee": {
+      "type": "integer"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "umaBond": {
+      "type": "integer"
+    },
+    "umaReward": {
+      "type": "integer"
+    },
+    "volume24hr": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "volumeNum": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds value by disclosing the cost ($0.001 USDC per call) and the byte-identical mapping to a specific API endpoint, which informs agents about financial implications and implementation details beyond the annotation hints.

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 description is two sentences, with the first enumerating all returned fields and the second covering cost and endpoint equivalence. It is information-dense without excessive padding. The main purpose is front-loaded, and every clause contributes value, though it could be slightly tightened.

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 single-parameter read-only tool with a high-coverage schema, an output schema (indicated in context), and annotations covering safety, the description is complete. It specifies the data returned, cost, and implementation mapping. It does not mention usage guidance or edge cases, but those are minor for this simple fetch tool.

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% because the only parameter (id) has a clear description in the schema: 'Polymarket numeric market id [required]'. The description adds minimal extra meaning—only reiterating 'one market id' and giving an example id—which does not significantly enhance the schema's already adequate explanation. Baseline 3 is appropriate.

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 states a specific verb ('records') and a precise resource ('one market id'), then enumerates the exact data fields returned (question, description, resolution source, outcomes, prices, volume/liquidity series, fees, CLOB token ids). This clearly distinguishes it from sibling list tools like market_poly_markets and market_poly_tags, which are implied to be broader in scope.

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 description implies usage by emphasizing 'one market id' but does not explicitly state when to prefer this over alternatives like market_poly_markets. It lacks a direct 'use this when...' or 'instead of...' statement. However, the purpose is clear enough that an agent can infer it is for detailed single-market data.

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

All Crypto Bot Audit + Market Data (x402 paid) 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?