BlindOracle

get_signal_accuracy

Retrieve historical signal accuracy metrics to evaluate and tune trading strategies. Returns overall, per-asset, and per-signal-type accuracy over a rolling window.

Instructions

Get historical signal accuracy metrics from SQLite store.

REQ-SIGNALS-005b: Returns real accuracy data (not "not_available"). BLP-031: Self-Improvement — enables strategy tuning based on outcomes.

Args: days: Rolling window in days for accuracy calculation (default 30).

Returns: Dict with overall accuracy, per-asset and per-signal-type breakdowns, and total signal counts.

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

Input Schema

Name	Required	Description	Default
`days`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. States 'Returns real accuracy data (not "not_available")', assuring data quality. Implies read-only operation. Could explicitly state read-only nature, but sufficient.

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

Conciseness4/5

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

Description is concise with clear Args and Returns sections. Includes requirement IDs that may be extraneous for an AI agent. Still well-structured and efficient.

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?

Output schema exists (context signals), so description needn't detail return values thoroughly. It provides a high-level overview of return content. Lacks error handling info, but acceptable for a simple tool with one parameter.

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

Parameters5/5

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

Schema description coverage is 0%, but description adds: 'days: Rolling window in days for accuracy calculation (default 30).' This explains the parameter's purpose and default value, fully compensating for schema lacking 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?

Clearly states 'Get historical signal accuracy metrics from SQLite store', specifying verb, resource, and data source. Distinguishes from sibling tool 'get_trading_signals' which likely returns current signals, not accuracy metrics.

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?

Mentions 'Self-Improvement — enables strategy tuning based on outcomes', indicating when to use. Does not explicitly state when not to use or alternatives, but context from sibling list makes usage clear.

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