blackwall-x402-guardrail
Server Details
Pre-signature x402 payment verdict (GO/HOLD/STOP) for AI agents, with a verifiable signed receipt.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 4.1/5 across 1 of 1 tools scored.
Only one tool exists, so no risk of ambiguity. The tool's purpose is clearly defined.
The single tool name 'forecast_payment' follows a clear verb_noun pattern, which is consistent and intuitive.
A single tool for a guardrail service feels borderline; while the tool is well-scoped to its specific function, the server could benefit from additional tools (e.g., to retrieve past verdicts or manage settings).
The tool covers the core payment forecasting functionality (sanctions, reputation, anomaly checks) and returns a signed receipt, but lacks any history or configuration capabilities, which would be minor gaps.
Available Tools
1 toolforecast_paymentAInspect
Pre-signature x402 payment verdict: GO / HOLD / STOP for paying a counterparty, from settlement reputation, price-anomaly (quoted vs the payee's own median), and OFAC sanctions — with a third-party-verifiable Ed25519 signed receipt. Verdict only; never takes custody. Free under $10 at risk; over that, returns an x402 payment challenge.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | Yes | e.g. USDC | |
| chain | Yes | e.g. base | |
| payer | No | agent's EVM wallet (optional; binds settlement) | |
| amount | Yes | amount as a decimal string, e.g. "0.09" | |
| context | No | {quoted_price_history, expected_recipient} | |
| agent_id | No | caller DID/identity | |
| resource | No | what's being paid for | |
| counterparty | Yes | recipient wallet from the 402 |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description discloses key behaviors: verdict-only non-custodial action, Ed25519 signed receipt, and cost conditions. It lacks details on failure modes or authorization.
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 concise sentences that front-load the purpose and critical details without any waste.
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?
The tool has 8 parameters and nested objects but no output schema; the description does not explain the structure of the return value or the meaning of GO/HOLD/STOP, leaving gaps.
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?
Schema coverage is 100% with descriptions, so the description adds minimal extra semantics beyond examples like 'e.g. USDC'. Baseline score of 3 is appropriate.
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 provides a pre-signature x402 payment verdict (GO/HOLD/STOP) based on specific factors, distinct from a payment execution tool.
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?
It specifies that the tool never takes custody and explains the free vs. challenge threshold, but does not explicitly mention when to avoid using this tool or provide alternatives.
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.
Discussions
No comments yet. Be the first to start the discussion!