OMENZ agent tools

tx_preflight

Transaction Preflight: GO or STOP before your agent pays an x402 endpoint. Checks it answers, the live price is within max_price_usd, payTo matches expected_pay_to, the network is allowed, the asset is a known USD stablecoin, and flags drift from the price you were quoted/listed. Never pays the target. By OMENZ. (MCP calls run in AYNE, the free playzone; production: POST https://www.omenz.org/api/tollbooth/v1/tx-preflight, $0.002 via x402.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "tx_preflight"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`method`	No
`networks`	No
`allow_testnet`	No
`max_price_usd`	No
`expected_pay_to`	No
`listed_price_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that it makes no payment, that it probes whether the endpoint answers, that it flags price drift, and that MCP calls run free in the playzone while production costs $0.002 via x402. It omits the shape of the result beyond GO/STOP and any failure/rate-limit behavior.

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?

The decision framing is front-loaded before the checklist of validations, so an agent reads the purpose first. A few fragments ("By OMENZ", the production URL/pricing parenthetical) add bulk but the pricing note is genuinely useful context.

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?

For a 7-parameter tool with no annotations and no output schema, the description covers nearly everything needed to call it correctly, including the cost model of the production endpoint. The main gap is that the output beyond "GO or STOP" and the role of the method parameter are not described.

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?

Schema description coverage is 0%, yet the prose explains the meaning of max_price_usd (live price ceiling), expected_pay_to (payTo match), networks/allow_testnet (network allowed), and listed_price_usd (drift against quote/listing). Only url and method are left without added semantics, which is a strong compensation for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Transaction Preflight: GO or STOP before your agent pays an x402 endpoint" gives a concrete verb, decision output, and resource. It then enumerates exactly what is validated (reachability, max_price_usd, payTo, network allowlist, stablecoin asset, price drift), which clearly separates it from the generic sibling "preflight".

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 your agent pays an x402 endpoint" pins down the moment of use, and "Never pays the target" clarifies the boundary of the operation. It does not explicitly say when NOT to use it or name an alternative tool, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OMENZ agent tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?