TWZRD Agent Intelligence

check_listing

Read-onlyIdempotent

Pre-spend check of one product against the published listing cards. Free, read-only.

Returns unknown_seller when no published card covers the product (not a clean seller),
expired when the card is past expires_at, check_failed when the card cannot be verified
or the declared price is above the advertised one, and advertised when a current card
matches. It never authorizes a payment: authorizes_spend is always false. needs_approval
is true for every result except advertised, and also for an advertised card that
advertises nothing, advertises no price, cannot check the declared price, or is
declared below its advertised price (an unverified discount, including zero). It does
not fetch the store page, open a checkout or move money.

Input Schema

TableJSON Schema

Name	Required	Description
`market`	No	Optional subject market (e.g. US); must agree with the card when given.
`product`	No	Optional subject product; must agree with the card when given.
`variant`	No	Optional subject variant (e.g. Ink); must agree with the card when given.
`merchant`	No	Optional subject merchant; must agree with the card when given.
`product_url`	No	The store product URL the agent is about to buy from. Matched exactly against the published card's next_hop URL, the same rule as the paid checkout brief.
`declared_unit_price`	No	Optional unit price the seller is asking, in USD. Above the card's advertised price is refused (phantom_markup_detected); below it is discount_unverified and needs approval.

Output Schema

TableJSON Schema

Name	Required	Description
`claims`	No	The card's claims (name, value, state, reason). Unknown claims stay unknown.
`digest`	No	sha256 of the matching card's exact text (get_claim); null for unknown_seller.
`reason`	Yes	Why: e.g. no_card_for_product_url, expired_claim, phantom_markup_detected, current_card.
`result`	Yes	unknown_seller \| expired \| check_failed \| advertised.
`expires_at`	No	Earliest claim expiry on the matching card.
`artifact_id`	No	The matching card's artifact id; null when no card covers the candidate.
`price_check`	No	verified \| discount_unverified \| unverified \| absent \| above_advertised \| invalid, when a price was declared or checked.
`needs_approval`	Yes	True for every result except advertised, and for an advertised card that advertises nothing, advertises no price, cannot check the declared price, or is declared below its advertised price: a human approves before any spend.
`authorizes_spend`	Yes	Always false. advertised is current evidence, never permission to pay.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / declared_unit_price / description

Previous value: -"Optional unit price the seller is asking, in USD. Above the card's advertised price is refused (phantom_markup_detected); below it is discount_unverified."New value: +"Optional unit price the seller is asking, in USD. Above the card's advertised price is refused (phantom_markup_detected); below it is discount_unverified and needs approval."

changedOutput schema / properties / needs_approval / description

Previous value: -"True for every result except advertised, and for an advertised card that advertises nothing, advertises no price, or cannot check the declared price: a human approves before any spend."New value: +"True for every result except advertised, and for an advertised card that advertises nothing, advertises no price, cannot check the declared price, or is declared below its advertised price: a human approves before any spend."

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / needs_approval / description

Previous value: -"True for every result except advertised, and for an advertised card that advertises nothing or cannot check the declared price: a human approves before any spend."New value: +"True for every result except advertised, and for an advertised card that advertises nothing, advertises no price, or cannot check the declared price: a human approves before any spend."

AddedSep 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Far exceeds the annotations: it enumerates every verdict (unknown_seller, expired, check_failed, advertised), states that authorizes_spend is always false, and spells out exactly when needs_approval is true, including edge cases like an unverified discount including zero. It also bounds side effects explicitly.

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 core purpose is front-loaded in one sentence and the verdict enumeration is information-dense rather than padded. The needs_approval sentence is long and clause-heavy, costing a little readability, but every clause carries distinct behavior.

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 read-only, idempotent verification tool with a full input schema and an output schema, the description supplies the decision logic (verdict meanings, approval rules, no-spend guarantee) an agent needs to interpret results, with nothing material 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 documents all six parameters in detail, including matching rules and price semantics. The description reinforces price behavior via the needs_approval logic but adds no syntax beyond what the schema provides, so the baseline 3 applies.

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 line states a specific verb and resource ('Pre-spend check of one product against the published listing cards') plus the cost/safety profile ('Free, read-only'). An agent can immediately distinguish this verification-before-buying tool from retrieval siblings like get_merchant_card or get_publication.

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?

Usage context is clear ('pre-spend check', the URL the agent is 'about to buy from'), and it plants exclusions ('It does not fetch the store page, open a checkout or move money'). However, it never names a sibling alternative such as get_shopping_check or low_level_preflight, so routing among the 27 siblings still requires inference.

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.