Crank Protocol

discover_strategies

Read-onlyIdempotent

Browse published strategies (read-only, free). Crypto-only.

strategy_type filters to one of the 16 Crank strategy types (empty = all). sort ranks by clones|sharpe|return|sortino|win_rate|drawdown (default clones). detail="concise" (default) trims each entry to template_id/strategy_type/ name/clone_count/is_verified/backtest_hash (template_id is the ID to chain into clone_strategy); "full" adds description/config_template/ performance_summary/eligibility/author_wallet/created_at.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	clones
`limit`	No
`detail`	No	concise
`caller_id`	No
`strategy_type`	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.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds genuinely useful behavioral context beyond that: the tool is free, crypto-only, and the detail parameter changes the shape of each returned entry. It does not mention rate limits or pagination, but this is not critical given the annotation coverage.

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

Conciseness5/5

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

Every sentence earns its place and the description packs filtering, ordering, default behavior, and output-shape semantics into a compact, structured format. It is information-dense without being bloated.

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?

The description covers the essential decision factors: scope, cost, platform limitation, filter semantics, sort semantics, and output shape. The output schema is also present, so return-value documentation is largely handled elsewhere. Minor omissions like limit bounds and caller_id semantics are not critical for a read-only browse 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?

The schema has no inline descriptions (0% coverage), so the description carries nearly the entire burden. It meaningfully explains strategy_type, sort, and detail, including allowed values and default behavior. However, limit and caller_id are not covered, even though limit's purpose is fairly inferable from its name.

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 opens with a specific verb and resource combination, 'Browse published strategies', and immediately distinguishes the operation as read-only, free, and crypto-only. It also explains how the returned template_id feeds into clone_strategy, which separates it from other strategy-related siblings.

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?

The description clearly frames the tool as a read-only strategy browsing utility and gives the selection conditions for filtering and sort modes. It also points forward to clone_strategy for the next step, but it does not explicitly say when to prefer this tool over strategy_list, get_strategy_leaderboard, or get_strategy_suggestions.

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?