Skip to main content
Glama

Search with live price and stock (paid)

live_search
Read-only

Paid: US$0.02 per call in USDC over x402 (or 20 prepaid credits). Product search across big retailers and brand stores (deepest in Australia, also US), with the top results checked on the retailer page at the moment of the call: live price, stock and whether the link still works. Not charged if no page could be read. Without payment the result is an x402 payment request; attach the signed payment at _meta["x402/payment"] and call again. For free results as last recorded, use search_products.

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": {
      "query": "<query>"
    },
    "name": "live_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to check live (default 3).
queryYesThe product, 2 to 6 words.
countryNoAU or US.
max_priceNoHighest price in the country's currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here and delivers: exact price (US$0.02/call in USDC over x402 or 20 prepaid credits), the billing exception when no page can be read, and the retry protocol (unpaid call returns an x402 payment request; attach signed payment at _meta['x402/payment'] and call again). That is precisely the behavioral context an agent needs before spending money.

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?

Dense but front-loaded — price and billing are stated first, which is the right priority for a paid tool, followed by scope and payment recovery steps. It is one long chain of clauses, and the payment-retry mechanics could be split out, but no sentence is wasted.

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 paid, metered search tool with no output schema and four fully documented parameters, the description covers cost, billing exceptions, payment recovery, geographic scope, and the free alternative. Nothing material is missing for correct invocation.

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 baseline is 3: query, limit (results to check live), country, and max_price are all documented in the schema. The description adds scope context (AU/US coverage, live-check semantics) but no parameter-level meaning beyond what the schema already states.

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 a specific verb and resource — product search across big retailers and brand stores — plus the distinctive scope (deepest in Australia, also US) and the key differentiator that top results are re-checked on the retailer page for live price, stock, and link validity. That contrast makes it immediately distinguishable from search_products and live_check.

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?

Explicitly routes the agent: 'For free results as last recorded, use search_products,' and states the paid path and its payment mechanics. It also covers the no-charge condition, so the agent knows the cost risk before invoking.

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.

Resources