Skip to main content
Glama

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

Free demo of a paid tool

get_demo
Read-only

Returns a real, cached example response of a paid tool for a fixed example input – free, to inspect the output format before paying.

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": {
      "tool": "<tool>"
    },
    "name": "get_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "x402_check",
      -  "web_markdown",
      -  "text_keywords",
      -  "text_readability",
      -  "base_wallet",
      -  "web_meta",
      -  "domain_check",
      -  "web_sitemap",
      -  "base_contract",
      -  "base_tx",
      -  "base_wallets",
      -  "eth_wallet",
      -  "eth_token_balance",
      -  "eth_contract",
      -  "eth_tx",
      -  "weather",
      -  "crypto_price",
      -  "web_product",
      -  "eth_block",
      -  "eth_token_supply",
      -  "eth_transfer_logs",
      -  "format"
      -]New value: +[
      +  "x402_check",
      +  "web_markdown",
      +  "text_keywords",
      +  "text_readability",
      +  "base_wallet",
      +  "web_meta",
      +  "domain_check",
      +  "web_sitemap",
      +  "base_contract",
      +  "base_tx",
      +  "base_wallets",
      +  "eth_wallet",
      +  "eth_token_balance",
      +  "eth_contract",
      +  "eth_tx",
      +  "weather",
      +  "crypto_price",
      +  "web_product",
      +  "eth_block",
      +  "eth_nonce",
      +  "eth_token_supply",
      +  "eth_transfer_logs",
      +  "format"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "x402_check",
      -  "web_markdown",
      -  "text_keywords",
      -  "text_readability",
      -  "base_wallet",
      -  "web_meta",
      -  "domain_check",
      -  "web_sitemap",
      -  "base_contract",
      -  "base_tx",
      -  "base_wallets",
      -  "eth_wallet",
      -  "eth_token_balance",
      -  "eth_contract",
      -  "eth_tx",
      -  "weather",
      -  "crypto_price",
      -  "format"
      -]New value: +[
      +  "x402_check",
      +  "web_markdown",
      +  "text_keywords",
      +  "text_readability",
      +  "base_wallet",
      +  "web_meta",
      +  "domain_check",
      +  "web_sitemap",
      +  "base_contract",
      +  "base_tx",
      +  "base_wallets",
      +  "eth_wallet",
      +  "eth_token_balance",
      +  "eth_contract",
      +  "eth_tx",
      +  "weather",
      +  "crypto_price",
      +  "web_product",
      +  "eth_block",
      +  "eth_token_supply",
      +  "eth_transfer_logs",
      +  "format"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the behaviorally important facts that the result is cached, corresponds to a fixed example input rather than the caller's input, and carries no cost. It does not say how large or how enveloped the response is, but the key caveat (data is not real for your input) is disclosed.

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?

One sentence, front-loaded with the action and resource, with the qualifiers (cached, fixed input, free) following immediately. No waste.

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?

For a single-parameter, no-output-schema preview tool, the description covers what is returned and why, and warns that the payload is a sample rather than live data. Only the response envelope/shape is left unstated, which is minor here.

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 coverage is 0%, so the enum of 23 tool names is undocumented in the schema, and the description only implies the mechanism via 'of a paid tool' and 'fixed example input'. An agent can infer the parameter names which paid tool to demo, but that inference is never stated outright.

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 ('Returns a real, cached example response of a paid tool') and pins down the scope ('for a fixed example input – free'). This distinguishes it from the sibling tools, which are the actual paid endpoints producing live data.

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?

'to inspect the output format before paying' gives a clear condition for use and implicitly tells the agent to call the real tool when actual data is needed. There is no explicit when-not or named alternative, but the pay-vs-preview split is unambiguous.

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