Crank Protocol

get_token_risk_assessment

Read-onlyIdempotent

Per-token risk roll-up over recently observed safety signals (free read).

Folds every non-expired signal for subject (symbol or mint) in the window into the worst risk level seen, a 0..1 risk score, a per-level count breakdown, and the contributing signals (worst-first). Complements -- does not replace -- get_risk_assessment (regime + position-size guards for deploying a strategy). Descriptive observed data only. Not financial advice.

Workflow: INTELLIGENCE / RISK step -- run before quoting or sizing an unfamiliar token; a critical safety signal is a hard skip condition.

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": {
      "subject": "<subject>"
    },
    "name": "get_token_risk_assessment"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`subject`	Yes
`caller_id`	No
`window_hours`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 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=true, idempotentHint=true, and destructiveHint=false. Description adds behavioral details: it folds all non-expired signals into worst risk level, provides risk score and breakdown, and lists contributing signals worst-first. It also states 'Descriptive observed data only. Not financial advice.' There is no contradiction with annotations.

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 composed of three short paragraphs. The first gives the core action, the second clarifies relationship to sibling tool, and the third provides workflow context. It is efficient with no wasted words, though the second paragraph could be slightly more compact. Overall well-structured and front-loaded.

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 (context signal), the description does not need to detail return format. It covers purpose, differentiation, usage guidelines, and key behavioral details. The missing parameter explanations (limit, caller_id) are minor gaps. For a tool with four parameters and a robust annotation set, the description is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no schema descriptions), so description must compensate. It explains the 'subject' parameter as 'symbol or mint' and implies window_hours by referring to 'the window'. However, 'limit' and 'caller_id' are not explained. This partial coverage means the description adds some value but is insufficient for a zero-coverage situation.

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?

Description clearly states the tool does per-token risk roll-up over observed safety signals, and explicitly distinguishes it from the sibling tool get_risk_assessment by noting it complements but does not replace that tool. The verb 'get' plus 'risk assessment' is specific, and the scope ('per-token', 'recently observed') is precise.

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?

Description provides explicit workflow guidance: 'INTELLIGENCE / RISK step -- run before quoting or sizing an unfamiliar token; a critical safety signal is a hard skip condition.' It also tells when not to use it by contrasting with get_risk_assessment. This gives the agent clear when-to-use and action-triggering instructions.

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?