Skip to main content
Glama

Solana Rug-Risk Check

rug_check_sample

Free sample rug-risk report (BONK) showing the output format of rug_check.

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_check_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful traits: the call is free and the payload is a canned sample for a single named token rather than a live analysis, which is exactly what an agent needs to avoid treating the result as real risk data. It does not say whether the output is static vs. freshly computed, nor when the sample was produced.

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?

A single front-loaded sentence with no filler: the nature of the artifact, the fixed token, and its relationship to rug_check all land in one clause. Nothing to trim.

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 zero-parameter, annotation-free, no-output-schema demo tool, the description supplies enough to call it correctly and interpret the response. The only real gap is that it never states the sample is static/live or that it is not a substitute for rug_check on an arbitrary token, which matters if an agent might mistake the BONK sample for a real result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The absence of inputs is consistent with a fixed-sample demo, even though the description does not explicitly say 'takes no arguments'.

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 deliverable (a rug-risk report sample) and scopes it to a fixed token (BONK), immediately distinguishing it from the sibling rug_check by framing it as an output-format demo. It stops short of naming rug_check as the tool to use for real analysis in the same breath, but the purpose is unambiguous.

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?

'Showing the output format of rug_check' implies when this is useful (previewing/illustrating what the real tool returns), and 'Free' hints it costs nothing. However, there is no explicit when-to-use vs. when-not guidance and no instruction to call rug_check for actual token analysis — the routing is left to inference.

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