Crank Protocol

get_my_pledge_status

Read-onlyIdempotent

Read your own on-chain Pledge record for a launch (free).

Returns how much this wallet has pledged, its share of the raise, its remaining headroom under the per-wallet cap, the projected pro-rata allocation, how much the liquidity release schedule has unlocked vs already released, and whether an on-chain refund is available (refunds open only if the raise FAILS its minimum).

Workflow: MONITOR step -- poll this between the cliff and full release to decide when a claim_ilo_tokens call is worth making.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "launch_id": "<launch_id>",
      "wallet_address": "<wallet_address>"
    },
    "name": "get_my_pledge_status"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, but the description adds valuable context beyond them: the call is free, refunds are only available when the raise fails its minimum, and it exposes partial unlock state that changes over time. These are exact behavioral expectations an agent needs.

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?

The description is front-loaded with the action and embedded with a clear field list and a useful workflow note. Some field enumeration overlaps with what an output schema would provide, but the detail is relevant and clearly organized.

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?

Given that an output schema exists, this description covers the key behavioral context: monitoring role, refund conditions, and the trigger for switching to claim_ilo_tokens. Missing details are the no-pledge edge case and how the agent learns the cliff/release window, but those gaps are minor.

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 compensates fairly well by tying the meaning of launch_id and wallet_address to 'a launch' and 'this wallet' and by introducing the per-wallet cap that the allocation logic depends on. It does not explicitly describe caller_id or provide ID/wallet formats, which keeps it from a 5.

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?

Opening with 'Read your own on-chain Pledge record for a launch' gives a specific verb, resource, and scope. The returned fields—pledge amount, share, cap headroom, pro-rata allocation, release schedule, refund availability—make the tool's purpose concrete and distinct from related ILO/claim 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 'Workflow: MONITOR step' sentence tells the agent to poll this between cliff and full release in order to decide when a claim_ilo_tokens call is worth making. That gives clear usage context and names the relevant alternative, though it doesn't explicitly enumerate when to prefer other read-only siblings.

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?