Skip to main content
Glama

Get one signal study

get_study
Read-onlyIdempotent

What historically happened to a crypto coin's price after a specific signal (e.g. RSI oversold, a 20% weekly drop, a breakout), measured on every past occurrence and compared with the coin's ordinary days. Returns case count, win rate, median move before and after trading costs, typical dip on the way, the luck probability after multiple-testing correction, and a 0-100 proof score. Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>",
      "signal": "<signal>"
    },
    "name": "get_study"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesTicker or slug, e.g. BTC or bitcoin
signalYesSignal id, e.g. rsi-oversold, weekly-drop-20, golden-cross

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds real value on top by disclosing the data source (Binance daily candles), the full contents of the result (case count, win rate, median move net of costs, dip, multiple-testing-corrected luck probability, 0-100 proof score) and the interpretation caveat that this is not a prediction. It stops short of stating behaviour for thin or nonexistent samples, e.g. a minimum case count or what an unknown signal id returns.

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 behaviour is front-loaded in the opening clause, and the enumerated metrics are dense but each one earns its place by telling the agent what it will get back in the absence of an output schema. The closing 'not financial advice' sentence is arguably dispensable boilerplate.

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?

With no output schema and only two well-documented parameters, the description correctly spends its budget describing the return payload and the data source, which is what is genuinely missing from structured data. The remaining gap is failure behaviour — unknown coin or signal id, or samples too small to be meaningful — which matters for a statistics tool.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters carry examples (BTC/bitcoin, rsi-oversold), so the schema already does this work. The description's illustrative signals (RSI oversold, 20% weekly drop, breakout) reinforce the shape of a valid signal id but add no syntax or format detail beyond the schema.

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 uses a precise framing — the historical price behaviour of one coin after one named signal, measured against its ordinary days — which is a specific verb+resource rather than a restatement of the name. It does not name or contrast any sibling tool, so an agent must infer that find_evidence and latest_signals serve different needs, keeping it at 4.

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

Usage Guidelines3/5

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

Usage is only implied: the description makes clear this is a per-coin, per-signal lookup, which implicitly excludes the list-style siblings, but there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative. An agent can infer the call context from the required coin+signal pair but gets no routing guidance.

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