Skip to main content
Glama

ClearMarket

by fyi.clearmarket

get_market

Fetch one market and judge whether its price can be trusted. Accepts whatever id you have: a ClearMarket id (CM-MKT-…), a venue-native market id or Kalshi ticker, or a market URL (best-effort — Kalshi tickers / a native id in the path resolve; for Polymarket pass the conditionId, not the slug URL). Returns: raw question, current price / implied probability, the Resolution Clarity Grade with rcg.score (0-100) and rcg.caps (a cap such as "uncommitted_placeholder" hard-limits the grade — that is why a single-source market can still be C), full resolution provenance (arbitration_model = who resolves it, named source, source_type, and a graded source_status on EVERY market: named / no-committed-source / none / unknown), the contract shape (direction, settlement_style, threshold), the canonical question_id where linked, and also_on (the same question priced on other venues). The returned market_id is ALWAYS the canonical ClearMarket id (CM-MKT-…) — store and reuse THAT, not the venue id. Use before trusting or acting on a price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idYesA ClearMarket id (CM-MKT-…), a venue-native market id / Kalshi ticker, or a market URL (best-effort: Kalshi URLs resolve; for Polymarket pass the conditionId).

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: it accepts multiple ID formats (best-effort for URLs), returns a canonical ID, and provides detailed output including trust judgment via rcg. No contradictions.

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?

The description is front-loaded with the core purpose, then efficiently details input and output. Every sentence serves a purpose; no redundancy.

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?

Despite no output schema, the description enumerates all return fields (question, price, rcg, provenance, shape, etc.) and explains the canonical ID reuse, making it complete for the tool's use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by noting best-effort resolution and instructing to pass conditionId for Polymarket, going beyond the schema's generic description.

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 clearly states the verb ('Fetch') and resource ('one market'), with a specific judgment function ('judge whether its price can be trusted'), which distinguishes it from sibling tools like 'get_event' or 'get_signal'.

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?

The description explicitly says 'Use before trusting or acting on a price,' providing a clear use case. It does not contrast with alternatives, but the context makes the tool's role evident.

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

All ClearMarket toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct resource: events, markets, signals, or catalysts. Descriptions clearly separate 'get_event' (full event record) from 'get_market' (single market with trust metrics) and listing tools from detail fetchers. No ambiguity.

Naming Consistency5/5

All tools follow a consistent 'verb_noun' pattern (get_event, get_market, get_signal, list_events, list_signals, list_upcoming_catalysts), with no mixing of conventions or inconsistent verbs.

Tool Count5/5

With 6 tools, the set is well-scoped for the domain. Each tool serves a clear purpose without redundancy, and the count is appropriate for both detail and overview retrieval.

Completeness4/5

The server covers core retrieval needs for events, markets, signals, and catalysts. A minor gap is the lack of a direct list markets tool, but markets are accessible through events and get_market. Overall, the surface is reasonably complete for a read-only data service.

Resources