Skip to main content
Glama

Token risk report

get_risk_report
Read-onlyIdempotent

Live risk data for lending against (or borrowing with) a token: how many price sources it has and whether they cross-check each other, how far back its pool price history goes, how much trading it would take to move its pool price 2x and 10x, USDC available to borrow against it, its active loan limit, and plain-language explanations of every flag. Use this before setting a lending limit on a token.

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": {
      "asset": "<asset>"
    },
    "name": "get_risk_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesToken contract address on Base (preferred) or its symbol, e.g. WETH, VIRTUAL, esALB
skip_depthNoSkip the pool depth calculation (faster)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds substantive value beyond them by describing the computed metrics the report contains (price-impact depth for 2x/10x moves, USDC borrowable, active loan limit) and the plain-language flag explanations — content the agent cannot get from the annotations or the input schema. Auth, rate-limit, and freshness behavior are unstated.

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?

Purpose is front-loaded, followed by a dense but purposeful enumeration of report contents, then a single usage sentence. The list of metrics is long but each item is a distinct field of the report, so nothing is clearly padding. Slightly heavy as one sentence, which costs it a point.

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?

With no output schema, the description carries the burden of conveying what comes back, and it does so item by item, including that flags come with plain-language explanations. For a two-parameter read-only report tool this is close to complete; only freshness and error behavior for an unresolvable symbol or address are missing.

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 description coverage is 100%, so both parameters are already documented, including the address-preferred-over-symbol guidance and the meaning of skip_depth. The description adds no parameter-level detail of its own, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource — live risk data for lending against or borrowing with a token — and enumerates the concrete dimensions returned (price sources and cross-checks, pool price history depth, 2x/10x price-impact depth, USDC borrowable, active loan limit, flag explanations). That is enough to distinguish it from get_market or request_token_listing without opening a schema. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

"Use this before setting a lending limit on a token" gives a clear, actionable trigger that ties the tool to the build_set_limits workflow. There is no when-not guidance and no alternative tool is named for the case where the agent only needs price or market data, which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.