Skip to main content
Glama

Safe-Send Check: crypto support triage, sanctions and scam screening

Buy credits with a plain USDC transfer: get a quote (free)

credits_quote

FREE, no x402 needed. Returns a quote id and the EXACT USDC amount to send on Base from your address to this service. After sending, call credits_claim with the quote id to receive an ssk_ key. 1 credit = $0.001 of list price (OFAC check 5, chat message 3, chat sweep of 25 messages 50, address check 1, payout list 50).

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": {
      "from": "<from>"
    },
    "name": "credits_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe Base address you will send the USDC from (0x + 40 hex). Only a transfer from that address can claim the quote.
packNostarter $0.25 (300 credits), team $1 (1,500 credits), ops $5 (9,000 credits). Default team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description usefully adds that the quote is free, that only a transfer from the stated address can claim it, and that claiming is a separate call. However, it never explains the consequence of idempotentHint=false (e.g., whether re-calling mints a new quote) or whether quotes expire, which are the main behavioral risks for this flow.

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?

Two dense sentences that front-load the free/quote/amount facts before the credit conversion table. The parenthetical cost list is long but each figure is actionable for an agent sizing a purchase; nothing is redundant.

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?

There is no output schema, and the description compensates by naming the two returned values (quote id and exact USDC amount) and the chain (Base). Quote lifetime/expiry and failure handling for an under- or over-payment are the only notable omissions for a two-call purchase flow.

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%, so both `from` and `pack` are already documented, including pack prices and credit amounts and the default. The description only reinforces the address-binding rule ('from your address to this service') and adds a credit-to-dollar conversion with per-operation costs, so it adds pricing context but little parameter syntax beyond the schema.

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 verb and resource ('Returns a quote id and the EXACT USDC amount to send on Base'), and the title frames the mechanics (plain USDC transfer, free quote). It also distinguishes the follow-up step by naming credits_claim, so an agent can tell this apart from the claim tool without reading either schema.

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?

'FREE, no x402 needed' signals this is the alternative to an x402 payment route, and 'After sending, call credits_claim with the quote id' gives an explicit next step. What's missing is an explicit statement of when to prefer this over the other payment route or what to do if the transfer never lands.

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