Skip to main content
Glama

textokit_polymarket_markets

Mercados y datos públicos de Polymarket. 0.002 USDC per call (x402, Base), first 10 calls/day per IP free; an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "textokit_polymarket_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoPublic wallet address required for positions and activity;…
limitNoUpstream page size before local filtering; defaults to 5. A…
orderNoDescending ordering within the received market page; missing…
queryNoCase-insensitive substring search in question and slug…
offsetNoOffset passed to the upstream endpoint before local…
statusNoFilter the received market page. Active requires active=true…
resourceNoDefaults to markets. Positions and activity require user.
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed8 schema fields changed
    • removedInput schema / allOf
      Removed value: -[
      -  {
      -    "else": {
      -      "not": {
      -        "required": [
      -          "user"
      -        ]
      -      }
      -    },
      -    "if": {
      -      "properties": {
      -        "resource": {
      -          "enum": [
      -            "positions",
      -            "activity"
      -          ]
      -        }
      -      },
      -      "required": [
      -        "resource"
      -      ]
      -    },
      -    "then": {
      -      "not": {
      -        "anyOf": [
      -          {
      -            "required": [
      -              "query"
      -            ]
      -          },
      -          {
      -            "required": [
      -              "status"
      -            ]
      -          },
      -          {
      -            "required": [
      -              "order"
      -            ]
      -          }
      -        ]
      -      },
      -      "required": [
      -        "user"
      -      ]
      -    }
      -  }
      -]
    • changedInput schema / properties / limit / description
      Previous value: -"Upstream page size before local filtering; defaults to 5. A filtered page may return fewer records or none."New value: +"Upstream page size before local filtering; defaults to 5. A…"
    • changedInput schema / properties / offset / description
      Previous value: -"Offset passed to the upstream endpoint before local filtering; defaults to 0. Endpoint-specific restrictions may cause an upstream error."New value: +"Offset passed to the upstream endpoint before local…"
    • changedInput schema / properties / order / description
      Previous value: -"Descending ordering within the received market page; missing numeric values sort last. Defaults to volume. Markets only."New value: +"Descending ordering within the received market page; missing…"
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
    • changedInput schema / properties / query / description
      Previous value: -"Case-insensitive substring search in question and slug within the received market page. Whitespace-only values are rejected. Markets only."New value: +"Case-insensitive substring search in question and slug…"
    • changedInput schema / properties / status / description
      Previous value: -"Filter the received market page. Active requires active=true and closed=false; closed requires closed=true. Defaults to all. Markets only."New value: +"Filter the received market page. Active requires active=true…"
    • changedInput schema / properties / user / description
      Previous value: -"Public wallet address required for positions and activity; rejected for markets."New value: +"Public wallet address required for positions and activity;…"
  3. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose pricing, the x402/Base payment rail, free-tier rate limit, and that unpaid calls return payment requirements — genuinely useful behavioral context. However it never states that the operation is read-only/non-destructive, nor describes the response shape or pagination semantics, which matter for an 8-param, no-output-schema tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, which is good, but the front-loading is off: payment mechanics dominate while the tool's actual function ('what does it return?') gets only a five-word noun phrase. Content is efficient but mis-prioritized for tool selection.

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?

Payment/auth completeness is strong, which is the main risk for this tool. But with 8 optional parameters, no output schema and no annotations, the description leaves the agent guessing about return values, page/local-filter interaction (limit/offset are passed upstream before filtering), and read-only safety — gaps that structured fields don't close.

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 is already documented upstream and the baseline applies. The description adds no parameter-level meaning — resource selection, user requirement for positions/activity, and the payment_signature alternative are all covered in the schema, not the prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the domain ('Mercados y datos públicos de Polymarket') but no verb — an agent can't tell it's a query/list tool that returns markets, positions or activity depending on the `resource` parameter. The name-plus-description combination is inferable but the scope is vague; sibling differentiation is limited to a pointer to textokit_sample.

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?

Provides clear usage context on cost (0.002 USDC per call, 10 free calls/day per IP) and names textokit_sample as the free alternative. But it never says when to pick this tool over siblings like textokit_crypto_prices or textokit_x402_ping, and gives no guidance on when positions vs activity resources are appropriate beyond what the schema already says.

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.