Skip to main content
Glama

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.

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

Input Schema

NameRequiredDescriptionDefault
price_usdcNoCaller-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_intentNoWhat the agent intends to do with the purchased response or tool.
buyer_walletNoBuyer's Solana wallet public key; enables buyer-context evidence in scoring.
resource_urlNoCanonical endpoint URL for the resource, if available.
resource_nameNoProvider or listing identifier to evaluate before payment.
seller_walletNoSeller payTo (Solana base58 or Base 0x address) for reputation and spend checks.
marketplace_scoreNoOptional marketplace-provided score (0-100) for blend-in scoring context.

Output Schema

NameRequiredDescriptionDefault
reasonNoDecision-consistent one-line rationale.
decisionNoSpend decision: "allow" | "warn" | "block". wash_flagged=true never soft-allows — this field is block (no warn/allow/quick).
evidenceNoEvidence bullets behind the decision.
trust_scoreNoComposite trust signal, 0-100. Null when TWZRD has no evidence about the subject (readiness_card.subject_known=false).
readiness_cardNoThe full ReadinessCard shape (same keys as get_readiness_card_tool).
full_report_hintNoHow to fetch the paid full report.
paid_quick_endpointNoFirst paid hop: $0.001 score-only teaser, if seller identity is known.
paid_trust_endpointNoOptional $0.05 V7 receipt path, if seller identity is known.
suggest_full_reportNoWhether to upsell the paid V7 receipt report.
max_spend_recommendation_usdcNoSuggested per-call spend ceiling for this decision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / trust_score / description
      Previous value: -"Composite trust signal, 0-100."New value: +"Composite trust signal, 0-100. Null when TWZRD has no evidence about the subject (readiness_card.subject_known=false)."
  2. Changed1 schema field changed
    • changedInput schema / properties / seller_wallet / description
      Previous value: -"Seller's Solana wallet public key for reputation and spend checks."New value: +"Seller payTo (Solana base58 or Base 0x address) for reputation and spend checks."
  3. Changed1 schema field changed
    • changedOutput schema / properties / suggest_full_report / description
      Previous value: -"Whether to upsell the paid v6-receipt report."New value: +"Whether to upsell the paid V7 receipt report."
  4. Changed2 schema fields changed
    • 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."
  5. Changed2 schema fields changed
    • 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)."
  6. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint and idempotentHint, it discloses hard-stop behavior: wash_flagged=true blocks rather than soft-allows, and unlabeled leftover 0.05/leftover=0 must not be read as a unit price. It also explains endpoint pricing and that the embedded readiness_card matches the get_readiness_card_tool output shape.

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 content is front-loaded with the tool's role and preferred alternative, and the hard-stop section is clearly separated. However, both hard-stop rules are stated twice almost verbatim, adding avoidable repetition.

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?

The output schema exists and the description appropriately references it while still explaining the key output flags and decision semantics. It provides enough context to choose and interpret this tool, though some of the domain jargon could be clearer for unfamiliar callers.

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 seven parameters are already documented in the schema. The description repeats the price_usdc caution but adds little new parameter meaning beyond what is already supplied.

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 identifies this as a low-level preflight check that returns a richer result object with paid endpoint data and an embedded readiness_card. It distinguishes itself from get_readiness_card_tool by naming the extra fields it exposes, though the exact object being preflighted is left somewhat implicit.

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?

It explicitly says to prefer get_readiness_card_tool for most callers and gives the precise conditions for choosing this tool: needing max_spend_recommendation_usdc, full_report_hint, or suggest_full_report. No alternatives or exclusions are left to inference.

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.