Skip to main content
Glama

Tested market hypotheses (confirmed and rejected)

hypothesis_ledger
Read-onlyIdempotent

Search INDICIA DESK's public registry of BTC/ETH market beliefs tested on its own data, including the rejected ones. Use when someone asks whether a popular crypto trading belief holds, e.g. "does max pain attract price?", "do whales lead the move?", "is selling volatility after a fear spike profitable?". Returns verdict status and a plain-language teaser; exact thresholds are not public.

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

Input Schema

NameRequiredDescriptionDefault
assetNoUnderlying asset.
groupNoFilter by verdict group.
limitNo
queryNoKeywords, e.g. "max pain", "whales", "skew", "funding".

Output Schema

NameRequiredDescriptionDefault
linkYes
as_ofYesUTC time the underlying data was computed.
staleYesTrue when the data is older than its normal refresh cycle.
caveatNo
sourceNo
summaryYes
age_hoursNoHours between as_of and the time of this answer.
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / age_hours
      Added value: +{
      +  "description": "Hours between as_of and the time of this answer.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so credit goes to the added context: results include rejected hypotheses (guarding against confirmation bias), each hit returns a verdict status plus a plain-language teaser, and exact thresholds are not public — a useful constraint on what the agent can promise a user. Pagination and auth details are absent, keeping it below a 5.

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?

Three sentences, front-loaded with the what and then the when, with no filler. The example questions are longer than strictly necessary but double as query-keyword guidance, so they earn their space.

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?

An output schema exists, so return values need only light framing, and the description supplies exactly that. For a four-param, all-optional search tool the definition is complete enough to invoke correctly; only edge details like the 25-result cap are left entirely to the schema.

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 coverage is 75% and two parameters carry enums, so the schema does most of the work. The description adds meaning mainly by supplying representative keywords ('max pain', 'whales', 'selling volatility') that illustrate what the query parameter matches, and by implying the group filter spans rejected as well as confirmed verdicts. It says nothing about the limit parameter's cap or default.

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?

States a specific verb and resource: search a public registry of BTC/ETH market beliefs that were tested on INDICIA DESK's own data. The phrase 'including the rejected ones' defines scope in a way that separates it from market_state or decision_journal, so an agent can recognize it without opening the schema.

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?

Gives an explicit trigger ('Use when someone asks whether a popular crypto trading belief holds') plus three concrete example questions that map to real invocation scenarios. It stops short of stating when not to use it or routing to a sibling tool, but the usage context is unambiguous.

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