Skip to main content
Glama

Conduit Agentic Commerce

Search supply

supply_search
Read-onlyIdempotent

Multi-provider discovery (live REAL merchants by default). Returns a ranked page (default limit=30, max 100) with total/has_more/next_offset. Follow next.args (search_id+offset+limit) to page without re-fanout. Optional fetch_limit (max 300) deepens the upstream pull on new searches. Pass include_sandbox=true only to append DEMO/SANDBOX test merchants at the bottom (test_offer=true). Always pass agent_id for mandate-aware badges. Carry search_id through supply_details / order_execute / order_feedback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size of ranked offers to return (default 30, max 100)
queryNoProduct search query, e.g. USB-C charger 65W. Required for a new search; omit when paging with search_id + offset
budgetNoMax total budget — number means USD; or { amount, currency }
offsetNo0-based offset into the ranked set for this search_id (default 0). For page 2+, pass search_id from the prior response and follow next.args
countryNoISO country for ships-to, e.g. US
agent_idNoAgent id for mandate-aware badges (always pass when available)
quantityNoDesired quantity (default 1)
search_idNoResume paging into a prior ranked set (with offset>0, or offset 0 without query). New searches with query mint a fresh search_id
fetch_limitNoOptional override for per-merchant upstream pull (default max(20, limit*2), max 300). Ignored when paging via search_id+offset
payable_withNoFilter to rails the agent can pay with, e.g. ["x402"]
session_tokenNoSession token from agent_authenticate — required whenever agent_id is passed
include_sandboxNoInclude DEMO/SANDBOX merchants (listed last, test_offer=true). Default false — live REAL merchants only. Use only when testing Conduit checkout flows.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
nextNo
errorNo
limitNo
totalNo
detailNo
offersNo
offsetNo
countryNo
partialNo
degradedNo
has_moreNo
withheldNo
search_idNo
next_offsetNo
recommendedNo
badge_countsNo
country_defaultNo
include_sandboxNo
sandbox_includedNo

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations: live-real-merchants default, ranked response with total/has_more/next_offset, no re-fanout paging, fetch_limit upstream pull, sandbox merchants appended at the bottom with test_offer=true, and mandate-aware badges. This is highly transparent for a read-only search tool.

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

Conciseness5/5

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

Five dense sentences, purpose first, then response shape, paging, optional fetch_limit, sandbox behavior, agent_id, and downstream handoff. Every sentence carries unique operational information with no filler.

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 12-parameter, 0-required tool with an output schema, the description covers the non-obvious control flow: new search vs paging, sandbox mode, fetch_limit, agent_id mandate context, and cross-tool search_id usage. Remaining parameter details are fully captured by the schema, so nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds workflow-level meaning: next.args paging semantics, fetch_limit's effect on upstream pull, search_id reuse, include_sandbox default and placement, and agent_id purpose. It does not merely repeat schema text; it explains why and how parameters matter.

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?

States it is a multi-provider discovery tool returning a ranked page of live REAL merchants, with explicit paging and sandbox behavior. The search_id carry-through sentence positions it against supply_details / order_execute / order_feedback, so an agent can distinguish it from those siblings.

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?

Provides concrete usage conditions: include_sandbox=true only for DEMO/SANDBOX merchants, fetch_limit only on new searches, always pass agent_id, and page via next.args without re-fanout. It does not explicitly state a 'use supply_details instead when...' alternative, but the workflow sentence strongly implies search precedes those downstream tools.

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.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools map to a distinct resource/action, and the descriptions explicitly call out boundaries (e.g., agent_notify targets Hub users while agent_outreach targets external addresses). A few closely related pairs such as supply_delivery/supply_details and order_events/order_track could still cause misselection despite the clarifying notes.

Naming Consistency4/5

Tool names follow a clear lowercase snake_case resource-prefix pattern across agent_, order_, payment_, and supply_. The pattern is not perfectly uniform because some names are noun-only (agent_organization, payment_methods, supply_details) and order_update_status is a longer compound.

Tool Count4/5

At 19 tools, the set is slightly above the ideal range, but the count is justified by four distinct subdomains: agent identity/communication, orders, payments, and supply. No obvious filler tools are present.

Completeness4/5

The surface covers the main commerce workflow well: agent setup/auth, search and delivery probes, order execution/tracking/feedback/disputes, and payment mandates/methods. Minor gaps like no agent deletion, no payment-method disable, and no standalone order-detail tool are workable or arguably out of scope.

Resources