TWZRD Agent Intelligence

low_level_preflight

Read-onlyIdempotent

Low-level preflight check. Returns a richer result object including
paid_quick_endpoint ($0.001 first hop) and optional paid_trust_endpoint ($0.05 V7).
wash_flagged=true never soft-allows. Unlabeled leftover 0.05 / leftover=0 is not a unit price.

Prefer get_readiness_card_tool for most callers. Use this when you need
max_spend_recommendation_usdc, full_report_hint, or the suggest_full_report
flag. The embedded `readiness_card` carries the SAME full shape as
get_readiness_card_tool (see the outputSchema).

Hard-stops:
  wash_flagged=true never soft-allows (decision=block; no warn/allow/quick).
  Unlabeled leftover 0.05 / leftover=0 is not a unit price; read readiness_card.price_kind.

Input Schema

TableJSON Schema

Name	Required	Description
`price_usdc`	No	Caller-supplied exact unit price in USDC. Leave unset unless you have an exact quote. Unlabeled leftover 0.05 / leftover=0 is not a unit price.
`agent_intent`	No	What the agent intends to do with the purchased response or tool.
`buyer_wallet`	No	Buyer's Solana wallet public key; enables buyer-context evidence in scoring.
`resource_url`	No	Canonical endpoint URL for the resource, if available.
`resource_name`	No	Provider or listing identifier to evaluate before payment.
`seller_wallet`	No	Seller's Solana wallet public key for reputation and spend checks.
`marketplace_score`	No	Optional marketplace-provided score (0-100) for blend-in scoring context.

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Decision-consistent one-line rationale.
`decision`	No	Spend decision: "allow" \| "warn" \| "block". wash_flagged=true never soft-allows — this field is block (no warn/allow/quick).
`evidence`	No	Evidence bullets behind the decision.
`trust_score`	No	Composite trust signal, 0-100.
`readiness_card`	No	The full ReadinessCard shape (same keys as get_readiness_card_tool).
`full_report_hint`	No	How to fetch the paid full report.
`paid_quick_endpoint`	No	First paid hop: $0.001 score-only teaser, if seller identity is known.
`paid_trust_endpoint`	No	Optional $0.05 V7 receipt path, if seller identity is known.
`suggest_full_report`	No	Whether to upsell the paid v6-receipt report.
`max_spend_recommendation_usdc`	No	Suggested per-call spend ceiling for this decision.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

addedOutput schema / properties / paid_quick_endpoint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "First paid hop: $0.001 score-only teaser, if seller identity is known.",
+  "title": "Paid Quick Endpoint"
+}

changedOutput schema / properties / paid_trust_endpoint / description

Previous value: -"Paid trust endpoint path, if seller identity is known."New value: +"Optional $0.05 V7 receipt path, if seller identity is known."

Changed2 schema fields changedSep 12, 2026

changedInput schema / properties / price_usdc / description

Previous value: -"Quoted payment amount in USDC for this intended request."New value: +"Caller-supplied exact unit price in USDC. Leave unset unless you have an exact quote. Unlabeled leftover 0.05 / leftover=0 is not a unit price."

changedOutput schema / properties / decision / description

Previous value: -"Spend decision: \"allow\" | \"warn\" | \"block\"."New value: +"Spend decision: \"allow\" | \"warn\" | \"block\". wash_flagged=true never soft-allows — this field is block (no warn/allow/quick)."

First observedJul 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Even with readOnlyHint and idempotentHint already present, the description adds materially useful behavior: wash_flagged=true never soft-allows and yields decision=block with no warn/allow/quick, and an unlabeled leftover 0.05 or leftover=0 is not a unit price. It also discloses pricing hints for the paid endpoints. These are non-obvious behaviors an agent needs to interpret results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and contains a clear 'Hard-stops' section, but it repeats 'wash_flagged=true never soft-allows' and 'Unlabeled leftover 0.05 / leftover=0 is not a unit price' in both the opening and the hard-stop list. The redundancy makes it less concise than it could be, though the length is still manageable.

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

Completeness5/5

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

For a low-level tool with 7 optional parameters and an output schema, the description covers the essential context: when to prefer the sibling, which output fields justify this tool, and what edge-case behaviors to expect. It points to the outputSchema for the readiness_card shape rather than duplicating it, so nothing critical is missing.

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 the schema already carries the parameter meanings, including the price_usdc leftover caveat. The description reinforces that caveat but does not add new per-parameter semantics beyond what the input schema provides. The baseline 3 is appropriate.

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?

The opening sentence names a specific operation—'low-level preflight check'—and states it returns a 'richer result object' with named fields such as paid_quick_endpoint and paid_trust_endpoint. It also distinguishes itself from get_readiness_card_tool by positioning itself as the lower-level variant that returns richer detail. This is enough for an agent to know what the tool does and how it relates to its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Prefer get_readiness_card_tool for most callers' and then states exactly when to choose this tool: when max_spend_recommendation_usdc, full_report_hint, or suggest_full_report are needed. It even explains that the embedded readiness_card has the same shape as get_readiness_card_tool, providing clear routing between alternatives.

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

All TWZRD Agent Intelligence 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.