Skip to main content
Glama

ClearMarket

by fyi.clearmarket

list_events

Browse or search ClearMarket prediction-market events. Filter by category, platform, Resolution Clarity Grade, or free-text q. q is token-AND across question + tags, so SHORT KEYWORD queries match best ("microstrategy bitcoin", "fed rate") — natural-language phrases often return nothing. Returns compact graded summaries: slug, question, venues_covered, primary grade, rcg_score (0-100, for ranking clarity), last_price, and status (open / resolved). Start here when you have a topic but not a slug; then call get_event for the full graded record. Categories: economics, financials, crypto, companies, technology, politics, geopolitics, health, climate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across event questions. Omit to list the whole filtered universe.
gradeNoResolution Clarity Grade of the primary market.
limitNo
offsetNo
categoryNo
platformNo

TDQS

A4.7/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It discloses search behavior (token-AND across question+tags), return format (compact graded summaries with listed fields), and the effect of category/platform filters. No security or rate-limit info, but for a read search tool this is adequate.

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 well-structured and concise: purpose, filter behavior, return fields, workflow advice, category list. Every clause adds value with 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?

Given 6 parameters, no output schema, and no annotations, the description covers all filters, explains return structure, and provides usage context. It is complete enough for an agent to effectively use this tool.

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?

Only 33% of parameters have descriptions in the schema, but the description compensates by explaining q's token-AND behavior and listing category options (though platform enum is not explicitly listed). This adds significant meaning beyond the schema.

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 tool browses or searches ClearMarket prediction-market events, with specific filters and return fields. It distinguishes itself from get_event by indicating that list_events is the starting point when a slug is unknown.

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?

Explicit guidance is given: start here when you have a topic but not a slug, then call get_event for full record. Also explains q's token-AND behavior and recommends short keyword queries, helping the agent avoid natural-language pitfalls.

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