Fetch one full CM Signal wire by slug: headline, the 3-5 structured bullets, atomic claims with per-field provenance tiers, the target + linked events, primary and related markets with prices, and sources. Use when you have a wire slug (from list_signals) and need the complete bulletin with its proof chain.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Wire slug, e.g. "us-iran-nuclear-deal-before-2027-polymarket-77-2026-05-29". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It accurately describes the tool as read-only ('Fetch') and details the comprehensive return contents (headline, bullets, claims, events, markets, sources). No side effects or permissions are needed, so the description 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero fluff. The first sentence immediately conveys what the tool does and returns, while the second provides usage guidance. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description thoroughly explains the return structure. It also references sibling tools (list_signals) to anchor usage. This is complete for a simple fetch tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'slug' has full schema coverage with an example. The description adds value by explaining its origin ('from list_signals') and context ('by slug'), making it clear how to obtain valid input.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Fetch' and the resource 'one full CM Signal wire by slug', and lists the included elements. It effectively distinguishes from siblings like list_signals (which provides slugs) and get_event/get_market (different resources).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Use when you have a wire slug (from list_signals) and need the complete bulletin with its proof chain', providing clear context for when to invoke. While it doesn't enumerate alternatives, the guidance is concise and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
