Skip to main content
Glama

ArcanumFleet Token Safety Audit

arcanum_audit
Read-onlyIdempotent

Use this when you have a specific Solana SPL mint address and need a full rug-check and safety verdict. For pool depth only, use arcanum_liquidity_check; for holder distribution, use arcanum_smart_money. Costs 0.005 USDC via x402.

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": {
      "mint": "<mint>"
    },
    "name": "arcanum_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesBase58 Solana SPL token mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mint / description
      Previous value: -"Solana token mint address"New value: +"Base58 Solana SPL token mint address"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds non-redundant context the annotations cannot express: this is a paid call costing 0.005 USDC via x402, which matters for an agent deciding whether to invoke. It stops short of describing what the verdict contains or whether results are cached.

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?

Two sentences, zero filler, with the use case front-loaded and the alternatives and cost following in descending order of importance. Every clause carries information an agent needs.

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 one-parameter read-only lookup with no output schema, the definition covers purpose, routing, and price, which is enough to call it correctly. The main remaining gap is that the composition of the "verdict" is never characterized, so an agent cannot anticipate the shape of the result.

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 100% and the single parameter is fully documented as a Base58 mint address, so the baseline applies. The description's phrase "specific Solana SPL mint address" echoes the schema rather than adding constraints such as mainnet-only or token-2022 handling.

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?

States a specific verb-and-resource pair ("full rug-check and safety verdict") tied to a concrete input ("specific Solana SPL mint address"), and explicitly contrasts its scope with two named siblings. An agent can distinguish it from arcanum_liquidity_check and arcanum_smart_money without opening either schema.

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?

Gives an explicit trigger condition ("when you have a specific Solana SPL mint address and need a full rug-check") plus routing rules for the two nearest alternatives, each with the condition that selects it (pool depth only, holder distribution). This is the when/when-not/alternatives pattern done properly.

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