Skip to main content
Glama

rug-check-service

rug_check

Paid Solana token rug-check ($0.25, or a bulk credit). If unpaid, returns HTTP-402-style payment instructions (receive-only address, memo, exact USDC/SOL amounts, expiry). After you pay from your own wallet, call again with memo and/or signature (or credit). Factual checks, not financial advice. Never holds keys and never sends funds.

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": "rug_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOptional referral code to attribute a later payment
memoNoInvoice memo from a prior unpaid result
mintYesSolana mint address (base58)
creditNoBulk credit_code from GET /credits
signatureNoConfirmed Solana transaction signature

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?

With no annotations supplied, the description carries the full burden and does well: it discloses the price, the exact unpaid behavior (HTTP-402-style instruction payload with address, memo, amounts, expiry), the custody posture ('never holds keys and never sends funds'), and the not-financial-advice disclaimer. It omits failure modes such as invalid or reused signatures, memo expiry, and lack of idempotency guarantees on repeated payment.

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?

Four tight sentences with no filler, and the price plus the unpaid-then-retry loop are front-loaded. The telegraphic style ('memo and/or signature (or credit)') is compact but slightly ambiguous about whether all are required.

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?

For a 5-parameter, paid tool with no annotations and no output schema, the payment side is thoroughly covered, but the successful result is not described at all — an agent cannot tell what a paid rug-check returns (risk flags, scores, which signals were evaluated). Payment mechanics are complete; result shape is a real gap.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is already documented. The description adds genuine semantic value beyond the schema by explaining the relationship between them: that memo comes from a prior unpaid result, that signature is obtained by paying from your own wallet first, and that credit or memo-and-signature are alternatives.

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?

It names a specific verb and resource — a paid Solana token rug-check — so an agent knows it produces a risk assessment on a mint address. It stops short of saying what the check actually inspects (holders, liquidity, mint authority) and never references the sample_check sibling to distinguish scope.

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?

The two-phase usage pattern is spelled out explicitly: call first, receive an unpaid payment-request payload, pay externally, then call again with memo and/or signature or a credit. Missing an explicit contrast with sample_check, which is the only sibling an agent might confuse it with.

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