Mekler AI

export_listings

Idempotent

Export up to 10000 visible x402 directory services with attributed source facts, measured health and grade history, first seen, scan counts, provenance and explicit truncation. Returns gzip+base64 JSON and a digest; large results use a 60 second signed download URL. Costs 0.25 USDC on Base or Solana. Reuse the original body and payment proof for exact 30 day result recovery. Never signs payments.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "export_listings"
  }
}

Input Schema

Name	Required	Description	Default
`idempotency_key`	Yes
`payment_signature`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: 0.25 USDC cost on Base or Solana, gzip+base64 JSON plus digest return shape, a 60-second signed download URL for large results, and the 30-day idempotent replay behavior. 'Never signs payments' also clarifies the safety boundary, which is consistent with readOnlyHint=false and idempotentHint=true.

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 the scope statement and every clause carries distinct information (cost, return format, recovery, safety). It is dense but not padded; a minor cost is that several facts are compressed into one run-on chain.

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?

With no output schema, the description usefully covers return encoding, digest, and the download-URL fallback, plus the payment flow and recovery semantics. It stops short of explaining what 'visible' filters out or the behavior on payment failure, but an agent can call it correctly.

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 0% for both parameters, so the description must compensate. It alludes to payment proof and body reuse for result recovery, which hints at payment_signature semantics, but never explains the idempotency_key's required format, uniqueness scope, or why it is mandatory.

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?

Specific verb (export) plus a precisely scoped resource: up to 10000 visible x402 directory services with named fields (source facts, health, grade history, first seen, scan counts, provenance). The bulk-export framing separates it cleanly from siblings like retrieve_listing, search_listings, and get_scan_report.

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?

It states cost, payment rails, and the 30-day recovery path, which implies this is a paid bulk operation, but it never explicitly says when to choose this over search_listings/search_services or what conditions make it inappropriate. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mekler AI 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.

Resources

Need Help?