Skip to main content
Glama

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

agent_preflight

[$0.05] Run real-time regulatory, SEC filing, 48h news velocity anomaly, and smart contract or domain security heuristics on any address, domain, or entity before transacting.

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

Input Schema

NameRequiredDescriptionDefault
targetNoTarget domain, smart contract address (0x...), or entity name
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful context: the $0.05 cost and the real-time nature of the checks, plus the degraded-timeout behavior documented in the schema. It says nothing about rate limits, auth requirements, or what the response payload contains, which is a meaningful gap for a tool with zero annotation coverage.

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?

A single dense sentence with the price tag front-loaded and the action immediately following. Every clause carries signal (cost, real-time, check families, target scope, trigger). The list of four check types makes it slightly heavy but nothing is wasteful.

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?

With only two simple parameters and no nested objects, the input side is well covered. However, there is no output schema and no annotations, so the description should ideally signal what a verdict or report looks like (scores? flags? narrative?) — that is the main missing piece for an agent deciding whether to rely on this output.

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 both parameters (target and timeout_ms) are already fully documented in the schema. The description's mention of 'address, domain, or entity' restates the schema's target description rather than adding new syntax or format detail, so baseline 3 applies.

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 verb ('Run') and enumerates the exact heuristic families applied: regulatory, SEC filing, 48h news velocity anomaly, and smart contract/domain security. It also names accepted target types ('any address, domain, or entity'), so an agent knows precisely what the tool produces. It stops short of explicitly contrasting itself with the similarly named security_preflight_402 sibling, so it does not fully earn a 5.

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?

The phrase 'before transacting' gives a clear, actionable trigger condition for when to call this tool. There are no explicit exclusions or named alternatives, but the pre-transaction framing is unambiguous enough for an agent to place the call correctly.

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