Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

security_preflight_402

[$0.001] Pre-flight x402 endpoint security firewall. Probes any x402 URL before payment to detect wallet-drain price spikes, SIWx origin spoofing, fake USDC contracts, and prompt injections.

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

Input Schema

NameRequiredDescriptionDefault
urlNoTarget x402 endpoint URL to inspect (https only)
methodNoHTTP method for the unpaid probePOST
deep_auditNoAdd one local-LLM prompt-injection audit of the 402 metadata
max_acceptable_usdNoYour maximum acceptable price in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose useful traits: a cost of $0.001, that the probe is unpaid, and the specific threat categories inspected. It does not state that the tool makes an outbound network request to a third-party URL (a real side effect), whether results are cached or persisted, rate limits, or what a pass/fail verdict looks like.

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?

Two tight sentences with the cost and the action front-loaded, then the threat list as supporting detail. No filler, no restatement of the title, and every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter security probe with full schema coverage, the description covers the 'what' adequately, but with no output schema present it should say what the agent receives back (a risk verdict, per-threat findings, a boolean safe-to-pay flag). It also omits the consequence of a failed probe, leaving the agent to guess at the result contract.

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 description coverage is 100%, so all four parameters are already documented, and the baseline of 3 applies. The description adds only indirect meaning — 'price spikes' loosely maps to max_acceptable_usd and 'prompt injections' to deep_audit — but gives no explicit parameter-level explanation beyond the schema.

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?

States a specific verb ('Probes'), a specific resource ('any x402 URL'), and enumerates four concrete threat classes it detects (price spikes, SIWx origin spoofing, fake USDC contracts, prompt injections). The x402 framing separates it from generic siblings like clean_url, though it never explicitly distinguishes itself from agent_preflight or agent_execution_firewall.

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?

'before payment' implies the trigger condition (run it prior to paying an x402 endpoint), but the phrasing is embedded in the purpose sentence rather than stated as guidance. There is no when-not guidance, no statement of what to do if the probe fails, and no explicit routing to or away from alternative preflight tools.

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