Skip to main content
Glama

My MCP Server

rug-pull-mint-auditor

Live Solana Mainnet rug-pull-mint-auditor ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

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": "rug-pull-mint-auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose genuinely useful non-obvious behavior: the call is live against Solana Mainnet and costs $0.10 USDC via an x402 v2 PAYMENT-SIGNATURE header, which tells the agent to expect payment handling. It says nothing about whether the call is read-only, what risks it detects, rate limits, or what the audit returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short parenthetical phrase with no wasted words, but the terseness comes from under-specification rather than economy. There is no front-loaded statement of what the tool actually does or returns.

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

Completeness2/5

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

With no annotations, no output schema, and zero parameter documentation, the description would need to explain both inputs and the audit's result shape; it explains neither. The payment and network disclosure is the only substantive addition, leaving the definition inadequate for a two-parameter financial-analysis tool.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters, 'mint' and 'targetWallet', and the description never mentions either. Neither name is defined, and both are optional (0 required), so an agent cannot tell whether targetWallet is the suspected rug-puller or the victim, nor what happens when it is omitted.

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

Purpose2/5

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

The text mostly restates the tool name plus environment and price; it names no verb and no resource beyond the compound name 'rug-pull-mint-auditor'. 'Live Solana Mainnet' adds environment context, but an agent must infer from the name alone that this analyzes a token mint for rug-pull risk.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any sibling such as holder-concentration-analyzer or spl-token-metadata-resolver that might overlap. An agent has no stated basis for choosing this auditor over the other token-analysis tools.

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