Skip to main content
Glama
Diogenes Web3, DeFi & HTTP 402 Security MCP

Diogenes Web3, DeFi & HTTP 402 Security MCP

solana_risk

Audit Solana SPL tokens to detect mint/freeze authority risks, holder concentration, and LP lock status before trading to assess rug-pull exposure.

Instructions

Audits Solana SPL token mint authority, freeze authority, top-holder concentration, and LP lock status.

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": {
      "token_address": "<token_address>"
    },
    "name": "solana_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_addressYesSolana mint or wallet pubkey

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully enumerates the four risk dimensions inspected, which is real behavioral content, but says nothing about whether the call is read-only, whether it touches external RPC/indexer services, rate limits, or what shape the findings take.

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?

One sentence, front-loaded with the verb and target, listing the checked dimensions without filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should set expectations about what comes back (a risk score, per-check flags, a verdict). It names the checks but not the resulting output, leaving the agent to guess the return shape for a tool whose entire value is the report.

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% with a single documented parameter ('Solana mint or wallet pubkey'), so the baseline is 3. The description only loosely narrows the input scope to SPL tokens and adds no format, encoding, or validation detail beyond the schema.

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?

States a concrete verb ('Audits') and a precise resource (Solana SPL token) and enumerates the exact checks performed (mint authority, freeze authority, holder concentration, LP lock). That is much more specific than a tautology. It does not, however, explicitly differentiate itself from the closest sibling (solana_whale_radar or contract_audit).

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

Usage Guidelines2/5

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

The description never says when to reach for this tool versus siblings like solana_whale_radar or contract_audit, nor does it name any prerequisite (e.g., that the input must be an SPL mint rather than an arbitrary account). Usage is only inferable from the tool name.

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