Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Structured product price & availability from a product page

web_product
Read-only

Structured product price & availability from any public product page: name, brand, SKU/GTIN, price, currency, availability, image and canonical URL, read from schema.org Product/Offer (JSON-LD or Microdata) with OpenGraph product meta tags as fallback. Respects robots.txt; no logins, no bot-protection bypass. Price: $0.003 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/web/product

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": {
      "url": "<url>"
    },
    "name": "web_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic product page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, yet the description adds real behavioral context beyond them: the extraction sources (schema.org JSON-LD/Microdata with OpenGraph fallback), the robots.txt/no-login/no-bot-bypass limits, and the per-call cost ($0.003 USDC via x402 v2 on Base). Missing only failure-mode detail, e.g. what is returned when no structured data is found.

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?

Front-loaded with purpose, then sources, then limits and pricing in a compact sequence. The field enumeration is long but functional, and the demo link plus price sentence earn their place for an agent deciding whether to call. No redundant restatement of the tool name.

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?

There is no output schema, but the description compensates by enumerating the returned fields and their extraction sources, and it discloses cost and access constraints. For a one-input extraction tool this is complete enough for an agent to call it correctly and predict the response shape.

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 single url parameter with its format, max length, and 'Public product page URL' description is already fully documented. The description reinforces the 'public' requirement and the robots.txt constraint but adds no syntax or format detail beyond the schema; 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?

States a specific verb+resource combination: extracting structured product price and availability from a public product page, then enumerates the exact fields returned (name, brand, SKU/GTIN, price, currency, availability, image, canonical URL). This clearly distinguishes it from generic page tools like web_markdown or web_meta.

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

Usage Guidelines3/5

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

Scope is implied ('any public product page') and constraints are stated (respects robots.txt, no logins, no bot-protection bypass), which tells the agent when the tool will fail. However, it never names or routes to alternatives such as web_markdown for non-product pages or web_meta for raw OpenGraph data, so selection guidance is only partial.

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