Skip to main content
Glama

ClearMarket

by fyi.clearmarket

list_signals

Browse the CM Signal daily wire — short, structured prediction-market bulletins (the price is the lede, news is context). Filter by event_id (every wire touching a specific event), category, venue, or detection type (news_cycle, cross_venue_divergence, benchmark_drift, volume_spike). Returns compact records, newest first; call get_signal for the full bulletin. Use to find ClearMarket's editorial read on what is moving.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
venueNo
categoryNoSignal category tag (case-insensitive): VS_BENCHMARK_DRIFT | CROSS_VENUE_DIVERGENCE | VOLUME_SPIKE | MOMENTUM_REPRICING | PRE_EVENT_PRICING. For thematic filtering use list_events.
event_idNoReturn only wires that target or link to this CM event_id.
detection_pathNo

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that the tool returns 'compact records, newest first' and lists available filters. It does not mention rate limits or authentication, but for a read-only list tool this is sufficient.

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?

Three sentences, each adding distinct value: purpose, filtering options, and guidance on sibling tools. No filler; front-loaded with the core function.

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?

Given no output schema, the description explains returns are 'compact records, newest first.' It mentions limit but not pagination details. Sibling tools are referenced for deeper context. Overall adequate for a list 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?

Schema coverage is 40%, but the description adds meaning for all parameters by explaining filtering semantics (e.g., 'every wire touching a specific event' for event_id). It also implies the limit parameter's default behavior. This compensates for schema gaps.

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 'the CM Signal daily wire — short, structured prediction-market bulletins' and specifies filters by event_id, category, venue, and detection type. It distinguishes from get_signal (full bulletin) and list_events (thematic filtering).

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?

Explicitly says to use this tool 'to find ClearMarket's editorial read on what is moving' and mentions alternatives: 'call get_signal for the full bulletin' and 'list_events for thematic filtering.' It also notes the default sort order 'newest first.'

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