SiteCheck

Search Panta prediction markets

markets

Read-only

Search Panta prediction markets (USDC on Solana) by keywords, phase or category. Compact rows: question, YES/NO implied probability from live prices, volume, close and resolution times, resolution source. Powered by Panta. Information only, not financial advice. Related tools on this server, for a different need: markets_brief when you need One Panta prediction market in depth: current YES/NO odds; markets_build_buy when you need to create an unsigned Panta buy transaction. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "markets"
  }
}

Input Schema

Name	Required	Description
`q`	No	Keywords, all must match (title, description, category)
`limit`	No	Max results, 1-20, default 10
`status`	No	primary (open for buys), secondary, resolved or cancelled
`category`	No	Optional: sports, crypto, politics, entertainment, finance, science, world, other

Output Schema

Name	Required	Description	Default
`total`	No
`results`	No
`poweredBy`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "disclaimer": {},
+    "poweredBy": {},
+    "results": {},
+    "total": {}
+  },
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's value-add is the cost model: '$0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged', which is critical pre-call context that cannot be inferred from structured fields. It also discloses data provenance (live prices) and the compact output shape. It omits rate limits or any latency expectations, keeping it short of a 5.

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?

Front-loaded with purpose, then output shape, then siblings, then price, so the most decision-relevant information comes first. A few clauses are low-value filler, notably 'Powered by Panta' repeated from the title and the generic 'Information only, not financial advice' disclaimer, but nothing is buried or contradictory.

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?

With an output schema present, the description correctly does not need to explain return values, and full schema coverage handles parameters. It closes the remaining agent-critical gaps with cost, payment chains, and alternative tool routing. Only pagination behavior beyond the limit parameter is left untouched.

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 the schema already defines q, limit, status, and category with defaults and enum-like values. The description only restates the filter axes as 'keywords, phase or category' without adding syntax, matching behavior, or tie-breaking rules, so it earns the baseline 3 rather than more.

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 and resource plus the filter axes: 'Search Panta prediction markets (USDC on Solana) by keywords, phase or category.' It also enumerates the returned row fields, and it explicitly names the sibling tools markets_brief and markets_build_buy as serving different needs, so the agent can distinguish it 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 Guidelines5/5

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

Provides explicit routing: use markets_brief for a single market in depth and markets_build_buy for an unsigned buy transaction, implying this tool is for broad discovery. The 'phase' and 'category' surfaces, along with the combination of keyword search with filters, make the use case unambiguous.

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

All SiteCheck 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.