Skip to main content
Glama

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

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices, the receiving address, the x402-over-MCP retry format, and how to use a prepaid credits key instead (bought with a plain USDC transfer, no x402 client needed).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely useful context beyond them: the leading 'FREE' tells the agent no payment or credits are consumed by calling this, and it discloses that a prepaid credits path exists requiring only a plain USDC transfer with no x402 client. It does not describe caching/refresh behavior, but nothing material is contradicted.

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, tightly packed sentence with the most decision-relevant fact ('FREE') front-loaded in caps. Every clause maps to a distinct returnable artifact, and there is no filler or redundancy.

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 carries the burden of describing return content, and it does so by enumerating the four things the caller gets back. It omits the response shape or format (e.g., whether the x402 retry payload is structured JSON ready to replay), which is a modest gap for a tool whose whole value is the format it returns.

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, which sets the baseline at 4. The description adds no parameter meaning because there is none to add, and the empty schema is fully consistent with a parameterless informational endpoint.

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?

The description names a specific resource and enumerates its contents: prices, receiving address, the x402-over-MCP retry format, and the prepaid credits key alternative. An agent can tell this is an informational/payment-instructions endpoint rather than a transactional one. It stops short of distinguishing itself from the adjacent credits_* siblings (notably credits_quote, which also concerns pricing), so the boundary is left slightly ambiguous.

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?

Usage is only implied: the mention of an 'x402-over-MCP retry format' hints this is what you call after a payment-required response, but the description never states that condition explicitly. There are no exclusions or named alternatives, so the agent must infer when to reach for this versus credits_balance or credits_quote.

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