Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.5/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly defined.
The single tool name 'check_payment_flow' uses a consistent verb_noun pattern, which is clear and predictable.
With only one tool, the server feels too sparse for a 'test suite' scope. Typically, a test suite would include multiple test tools or supporting operations.
The server provides only a single test operation, leaving obvious gaps such as setup, teardown, or additional payment flow tests. This significantly limits its usefulness.
check_payment_flowCheck x402 payment flowAInspectVerifies an agent's x402 payment flow against a free Base Sepolia testnet endpoint. Call with no arguments first to get back the payment-required challenge (price, network, payTo). Sign it with your x402 client, then call again passing paymentSignature as the encoded PAYMENT-SIGNATURE header value to get back a verified/failed receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| paymentSignature | No | Encoded PAYMENT-SIGNATURE header from a signed x402 payment payload. Omit to receive the payment-required challenge instead. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the two-step interaction, the challenge contents (price, network, payTo), and the outcome (verified/failed receipt). It implies a non-destructive verification, which is appropriate. No behavioral surprises.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, perfectly front-loaded, zero wasted words. Every sentence serves a purpose: first defines the tool, then explains the two-step process. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one optional parameter and no output schema, the description fully explains the workflow, expected inputs, and possible outcomes. It provides enough context for the agent to use it correctly without additional documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes paymentSignature as 'Encoded PAYMENT-SIGNATURE header'. The description adds significant value by explaining that omitting it returns a challenge and including it returns a receipt. This clarifies the parameter's role in the flow beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool verifies an x402 payment flow against a specific testnet endpoint. It distinguishes the two-step process: first without arguments to get a challenge, then with paymentSignature to get a receipt. This is specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage steps: call with no arguments first, then call again with paymentSignature. It tells the user what to expect at each step, giving clear context for when to use each variant. It does not explicitly state when not to use it, but the flow is well-defined.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!