Skip to main content
Glama

Verify payment, get a Pro key

verify_payment_and_get_key
Idempotent

After paying a quote, verify the Solana transaction on-chain (correct recipient, amount worth at least 95% of the price, carries the quote reference, confirmed, under 7 days old) and receive a RugRadar Pro API key valid for 30 days per payment. Idempotent: the same signature with the same order returns the same key; a signature can only be redeemed once.

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": {
      "signature": "<signature>",
      "order": "<order>"
    },
    "name": "verify_payment_and_get_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesThe order token from get_pro_quote
signatureYesSolana transaction signature of the payment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare openWorldHint and idempotentHint, but the description goes well beyond them: it enumerates the exact verification criteria (correct recipient, amount ≥95% of price, quote reference present, confirmed, under 7 days old), the key lifetime (30 days per payment), and the precise idempotency and single-redemption semantics. The non-readOnly stance is consistent with minting a key, so there is no contradiction.

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?

Three sentences, front-loaded with the action and the validation contract, then key lifetime, then idempotency. Every clause carries operational information — no restatement of the title or schema.

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?

With no output schema, the description correctly discloses that the return value is a Pro API key valid for 30 days. The main remaining gap is failure behavior: it does not say whether a failed verification returns an error code, a reason string, or a partial result, which matters for an open-world payment check.

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 both parameters are already documented as the order token and the Solana transaction signature. The description adds genuine meaning by defining what a *valid* signature must satisfy (recipient, 95% amount floor, quote reference, confirmation depth, 7-day age window), which tells the agent what inputs will succeed rather than just their format.

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?

States a specific two-part verb+resource: on-chain verification of a Solana payment transaction plus issuance of a RugRadar Pro API key. It is clearly distinguishable from get_pro_quote (which produces the quote referenced by the `order` parameter) and from get_pro_status.

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 opening clause 'After paying a quote' establishes both the precondition and the ordering relative to get_pro_quote, and the schema ties `order` back to that tool. It stops short of naming an alternative for the already-have-a-key case (e.g. get_pro_status) or stating what to do when verification fails, so usage is clear but not exhaustively routed.

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.