Coil Live

get_crypto_night

Read-onlyIdempotent

Which crypto coin has the strongest overnight momentum? The crypto book's overnight lane: one session-momentum read into the daily signal, with its study receipts. Overnight crypto continuation PREVIEW: the #1 session-momentum coin (of the top-5) heading into the 20:00 UTC signal across 81 Robinhood-tradable coins, plus the BTC 200-day regime gate, the pre/post-signal phase and the pre-registered study receipts. The ranking beat its random null at every fee tier in the cold study; at Robinhood retail fees the studied trade was REFUTED (the refutation ships in the read). A state read, not advice. Free.

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_crypto_night"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses that this is a free state read rather than advice and prominently warns that the studied trade was refuted at Robinhood retail fees despite cold-study ranking results. That is meaningful behavioral and evidentiary context, though data freshness, as-of behavior, and update cadence remain unspecified.

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

Conciseness3/5

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

The opening question is accessible, but the concrete output is delayed until the third sentence after two overlapping summaries. Repeated phrases such as “session-momentum” and “study receipts,” along with jargon like “crypto book’s overnight lane” and “cold study,” make the description denser than necessary.

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?

For a no-argument tool without an output schema, it usefully covers the ranking, universe, signal time, regime gate, phase, receipts, and study limitation. Nevertheless, the missing preview-versus-live distinction and freshness/as-of semantics are important selection gaps, while several domain terms are left unexplained.

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?

The tool has no parameters, so the zero-parameter baseline of 4 applies and no invocation syntax needs explanation. The universe, timing, and phase details help interpret the read even though they are not configurable inputs.

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 identifies a specific read: the leading session-momentum coin among the top five, drawn from 81 Robinhood-tradable coins ahead of the 20:00 UTC signal, with a BTC regime gate and study receipts. “Overnight” and “PREVIEW” narrow its scope, but it never explicitly explains how it differs from get_crypto_night_live.

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?

It clearly frames the intended situation as an overnight continuation preview heading into the daily signal, including pre/post-signal phase information. However, it gives no explicit when-not guidance or alternative routing, particularly for choosing between this preview and the live sibling.

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

All Coil Live tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?