Skip to main content
Glama

Quote for RugRadar Pro

get_pro_quote
Read-only

Get a payment quote for RugRadar Pro ($9 for 30 days, no auto-renewal): the exact USDC and SOL amounts, the Solana pay-to address, a unique reference to include in the payment (as a Solana Pay reference key or in an SPL Memo), a signed order token, and x402 details when available. Does not move funds; the agent or its user must send the payment from their own wallet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds meaningful behavior beyond them: no auto-renewal, 'does not move funds', the need for the agent/user to pay from their own wallet, and conditional x402 details. It stops short of noting quote expiry or whether the reference is single-use.

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?

Front-loaded with the verb and subject, then a colon-delimited list of returned values, closed by a single boundary sentence. It is somewhat long and dense, but every clause contributes to understanding what will be returned.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, but it omits lifecycle details an agent would need in practice (quote expiration, whether the reference can be reused, what happens if payment amount is wrong). For a payment-flow tool those gaps matter.

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 no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The enumerated return fields are useful, but they describe output rather than compensating for any parameter gap.

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?

Names a specific verb and resource ('Get a payment quote for RugRadar Pro'), pins the price and term ($9/30 days, no auto-renewal), and enumerates exactly what the quote contains. It is clearly distinguishable from verify_payment_and_get_key or get_pro_status by being the pre-payment quote step.

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?

Gives strong context on how the quote is consumed: include the reference as a Solana Pay key or SPL Memo and send funds from your own wallet. It does not explicitly name the follow-up tool or state when not to call this, so routing to verify_payment_and_get_key is left implicit.

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.