Skip to main content
Glama

Find the strongest studies

find_evidence
Read-onlyIdempotent

Lists the coin-and-signal studies with the strongest historical evidence, best first. Filter by coin, by signal, by lean (bullish or bearish) and by minimum proof score (default 55). Answers questions such as "which crypto signals actually worked" or "what has worked on ". Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

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

Input Schema

NameRequiredDescriptionDefault
coinNo
leanNo
limitNo
signalNo
min_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are ordered best-first, the min-score default is 55, and statistics are computed on Binance daily candles. It omits pagination/result-count behavior and any statement about how many records come back by default.

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?

The core capability and sort order are front-loaded in the first sentence, and filtering plus the default follow immediately. The trailing disclaimer is short and arguably functional for agent framing, but the example-question sentence is the least essential line.

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

Completeness3/5

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

With no output schema, the description should hint at what a returned study contains, but it only says studies are ranked "best first"; it never describes the fields of a study or what a proof score represents. The data source and default threshold are covered, but result shape and the undocumented `limit` leave real gaps for a 5-parameter 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 description coverage is 0%, so the description must carry the parameter burden, and it explains four of five: coin, signal, lean (bullish/bearish, also an enum in schema), and min_score with its default of 55. The `limit` parameter is never mentioned, leaving result-count control undocumented in both places.

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?

"Lists the coin-and-signal studies with the strongest historical evidence, best first" gives a specific verb (lists), resource (studies), ranking criterion, and sort order. It implicitly separates itself from get_study (singular) and latest_signals, but never names a sibling to make the boundary explicit.

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?

Example questions ("which crypto signals actually worked", "what has worked on <coin>") give the agent a clear sense of when this tool fits, and the mention of filters shows the intended narrowing workflow. It stops short of stating when NOT to use it or which sibling to prefer for a single study or for recent signals.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources