Crank Protocol

get_market_briefing

Read-onlyIdempotent

Crypto market briefing synthesised from free public sources (tiered).

Returns a market briefing aggregated from free crypto data sources (Coin Bureau, DeFiLlama, the alternative.me Fear & Greed index) plus classified sentiment signals: market summary, top movers / most-discussed assets, sentiment regime, the Fear & Greed reading, and source attribution. assets is an optional list of tickers (e.g. ["BTC","SOL"]); for paid tiers it declares the agent's holdings and focuses the synthesis. detail_level: "free" returns the pre-generated daily Free briefing (metered at $0, quota'd per day); "pro" ($0.25) and "platinum" ($0.50) return real-time synthesis by a larger model, personalised to the wallet's portfolio + active strategies. Paid tiers are covered by an active $CRANK-staker subscription or require a verified x402 payment_header (PAYMENT_REQUIRED otherwise). The billing outcome is in the response billing field. Not financial advice.

detail (payload shape -- NOT the pricing tier, that's detail_level above): "concise" (default) drops the long content body + model_used/source_count, keeping the summary, sentiment regime, Fear & Greed reading, covered assets, and strategy_connections (IDs for chaining into a strategy tool) plus the billing outcome; "full" returns every field exactly as before, including content.

Workflow: INTELLIGENCE step (usually first) -- macro/sentiment context that frames detect_regime + the allocation. See get_trading_workflow.

Input Schema

TableJSON Schema

Name	Required	Default
`assets`	No
`detail`	No	concise
`caller_id`	No
`timeframe`	No	24h
`detail_level`	No	free
`payment_header`	No
`wallet_address`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 23, 2026
- addedInput schema / properties / detail
```
Added value: +{
+  "default": "concise",
+  "type": "string"
+}
```
First observedJul 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover read-only, idempotent, open-world safety, but the description adds substantial behavior: the free tier is metered and quota'd, pro/platinum require an active $CRANK subscription or verified x402 payment_header, billing outcome is returned, and exact detail payload differences are explained.

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?

It is front-loaded with purpose and billing context, then workflow and payload details. The structure is clear and mostly earns its length, though there is minor redundancy between the first two sentences and some verbosity around tiers.

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

Completeness5/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 not be fully explained, but the description still clarifies the billing field and detail payload shape. Given seven optional parameters, annotation coverage, and an output schema, it supplies enough context for correct invocation.

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?

With 0% schema description coverage, the description carries the burden and explains assets, detail_level pricing tiers, detail payload shape, payment_header, and wallet_address personalisation. However, caller_id and timeframe are left unexplained, so it is strong but not complete.

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?

The description states a specific verb and resource: returns a crypto market briefing aggregated from named public sources plus sentiment signals. It also distinguishes its role from siblings by positioning it as the INTELLIGENCE step that frames detect_regime and the allocation, rather than being a regime detector itself.

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

Usage Guidelines5/5

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

It explicitly says this is usually the first step, used for macro/sentiment context, and points to get_trading_workflow for the broader workflow. It also gives clear conditions around free vs paid tiers and billing prerequisites.

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

All Crank Protocol 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?