Skip to main content
Glama

rug-check-service

sample_check

Free sample Solana token rug-check. Same report shape as a paid check. Factual public-data checks (mint/freeze authority, LP lock, top-10 holders, transfer fees), not financial advice. Never asks for a key or seed phrase.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana mint address (base58)

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?

With no annotations, the description carries the full burden and does reasonably well: it discloses that checks use factual public data (mint/freeze authority, LP lock, top-10 holders, transfer fees), that the report shape matches the paid tier, and that no key or seed phrase is ever requested. It stops short of stating rate limits, latency, or whether the free tier truncates the report.

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?

Three short sentences, front-loaded with what the tool is and how it relates to the paid version; the safety and disclaimer clauses are brief and relevant. Minor boilerplate ('not financial advice') but nothing bloated.

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 check with no output schema, the description covers purpose, data sources, safety posture, and report parity well. What the returned report actually contains field-by-field is left implicit, which is acceptable given the described parity with the paid check.

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% with a single required 'mint' parameter already documented as a base58 Solana mint address, so the baseline is 3. The description adds no format, validation, or edge-case guidance (e.g. malformed or non-mint addresses) 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 specific verb and resource ('Solana token rug-check') and narrows it to a free sample with 'same report shape as a paid check', which implicitly distinguishes it from the paid sibling. It never names rug_check outright, so the differentiation is inferential rather than explicit.

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?

The 'free sample' framing implies this is the preview path before a paid check, and listing the covered checks implies scope. However, there is no explicit statement of when to prefer this over rug_check, nor any exclusion such as chains or token types that are unsupported.

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