Skip to main content
Glama

Solana Signal

Token risk report (demo, JUP)

token_risk_demo
Read-only

Free, unlimited sample of the Solana token risk report (for the JUP token) so you can see the output format: 0-100 risk score, verdict, flags (mint/freeze authority, Token-2022 extensions, liquidity, age, holder concentration), market data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "token_risk_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely useful context: it is free and unlimited, it is hard-coded to JUP only, and it enumerates the report contents (risk score, verdict, flags, market data). Without an output schema, this preview of return fields carries real weight, though it does not say whether output is deterministic or time-sensitive.

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?

A single front-loaded sentence that leads with 'Free, unlimited sample' and then itemizes the output. It is dense but nearly every clause earns its place, with only mild run-on density from the parenthetical flag list.

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?

For a zero-parameter demo tool with no output schema, the description supplies the key missing information: the fixed token, the cost model, and an outline of return fields. An agent has enough to decide whether this preview is what it needs, though the enumeration of flags is summarized rather than fully specified.

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?

With zero parameters, the baseline is 4, but the description could do more to explain why none are needed — the fixed-JUP scope is stated as a fact rather than as the reason the tool takes no arguments. The schema is empty and therefore fully self-consistent; the description adds only the token identity.

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 precisely what the tool returns and its scope: a free, unlimited sample of the Solana token risk report, fixed to the JUP token, intended to demonstrate the output format. The word 'sample'/'demo' distinguishes it from the full-risk sibling token_risk, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'so you can see the output format' — an agent can infer this is for previewing the report shape rather than for analyzing an arbitrary token. However, there is no explicit instruction to use token_risk for real analysis or for other tokens, and no statement of when this tool should be preferred over alternatives.

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.

Resources