BlindOracle

analyze_all_markets

Aggregate and analyze prediction markets across Kalshi and Polymarket, with oracle verification via Chainlink and arbitrage detection for aligned market insights.

Instructions

Analyze all prediction markets with oracle verification @requirement: REQ-AGG-001 - Unified market aggregation @requirement: REQ-BLP-001 - Alignment tracking Properties: Alignment(+0.5), Self-Improvement(+0.3)

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

Input Schema

Name	Required	Description	Default
`find_arbitrage`	No
`include_kalshi`	No
`include_polymarket`	No
`include_chainlink_verification`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only mentions 'analyze' and 'oracle verification' without explaining side effects, resource usage, or what happens during analysis. The cryptic properties (Alignment, Self-Improvement) add confusion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but includes irrelevant requirement tags and property lines that clutter the core message. It could be more structured by separating the purpose from metadata.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema and multiple sibling tools, the description fails to explain the output format, integration with other tools, or how optional parameters affect behavior. It feels incomplete for a complex analysis tool.

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

Parameters1/5

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

The input schema has 4 optional parameters but the description provides no explanation of them. With 0% schema coverage, the description should compensate but does not even mention parameters, leaving agents to infer from parameter names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool analyzes all prediction markets with oracle verification, distinguishing it from sibling tools that focus on individual markets or trading. However, it does not explicitly differentiate from tools like submit_comprehensive_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_market_details or submit_oracle_job. The description lacks context about prerequisites, exclusions, or typical use cases.

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