Crank Protocol

get_ilo_details

Read-onlyIdempotent

Read a token launch live from chain (free): terms, status, escrow balances, and a machine-readable liquidity release schedule.

launch_id is the on-chain u64 launch identifier. Returns the raise window and progress, the per-wallet pledge cap (0 = uncapped), live escrow

launch-vault balances, and a release_schedule block (cliff-then-linear) an agent can plan future claim_ilo_tokens calls from without parsing prose. Pass caller_wallet to attach that wallet's own pledge summary too (the authoritative per-wallet view is get_my_pledge_status).

Utility token fair launch: participating commits funds to a non-custodial escrow; it is not a purchase of an expectation of profit.

Workflow: DISCOVER step -- read details, check the window and the per-wallet cap, then preview with pledge_to_ilo (plan mode) before committing anything.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`caller_id`	No
`launch_id`	Yes
`caller_wallet`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior; the description adds materially to that by clarifying the tool reads live on-chain data, is free, returns a machine-readable schedule for planning claim_ilo_tokens calls, and that escrow is non-custodial. This helps reason about side effects and timing without contradicting annotations.

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?

The description is carefully structured: a one-sentence overview, a backtick-delimited note on launch_id, then the caller_wallet caveat, the fair-launch usage context, and the recommended workflow. Every sentence earns its place, and the important usage guidance is front-loaded.

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?

Given the rich annotations, an output schema, and the description's own enumeration of the returned content, nothing essential is missing. The description covers purpose, key parameters, workflow, alternative tools, and behavioral caveats.

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 shoulders the burden for parameter meaning. It clearly explains launch_id as an on-chain u64 identifier and explains the optional caller_wallet effect and cap semantics (0 = uncapped). However, the caller_id parameter is never mentioned, which is a small but real gap.

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: 'Read a token launch live from chain', and enumerates the concrete data returned: terms, status, escrow balances, and release schedule. It also explicitly differentiates itself from get_my_pledge_status, so an agent can distinguish which tool is authoritative for per-wallet data.

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?

The description provides a concrete workflow: use it in the DISCOVER step, read details, check the launch window and per-wallet cap, then preview with pledge_to_ilo before committing. It also names get_my_pledge_status as the authoritative per-wallet alternative, making routing decisions explicit.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation2/5

Multiple tools overlap significantly: close_perp_position vs perp_close, get_leaderboard vs get_score_leaderboard vs get_strategy_leaderboard, get_venue_status vs get_all_venues_status, send_token_social vs bulk_send_social, and get_crank_score vs get_score. Several read-only tools have nearly identical purposes, and the descriptions do not always clarify boundaries.

Naming Consistency4/5

Most tools follow a consistent verb_noun snake_case pattern (get_balances, create_strategy, set_alert, list_webhooks). However, there are deviations like 'lst_swap', 'jupiter_swap', 'flash_loan', 'sr_backtest', and the use of both 'get_' and 'list_' for reads, plus category prefixes like 'perp_' and 'strategy_' that vary in order. Overall still readable and predictable.

Tool Count1/5

177 tools is an extreme count for any server, far exceeding the 25+ threshold for 'too many'. Even a full DeFi platform does not need this many separate operations; the surface is overwhelming and clearly not well-scoped.

Completeness3/5

The domain (Solana DeFi trading) is covered extensively across swaps, perps, lending, staking, strategies, signals, and support. However, there are notable gaps: no lend_withdraw, no direct way to close a lending position, no spot order cancellation (though aggregator-based swaps may not need it), and a general lack of tiered account management. The huge number of tools makes it hard to identify missing lifecycle steps.

Resources

Need Help?