AgentDiet Universal A2A & MCP Tool Discovery, Safe-Proxy & Swarm Router

execute_marketplace_tool

Read-onlyIdempotent

Execute any of the 16 native AgentDiet B2A tools by slug or proxy an external marketplace tool URL ($0.001-$0.02 per call). WHEN TO USE: Call to run a single tool discovered via search_x402_mcp_marketplace; use execute_workflow_bundle when you want to run a 4-tool composite bundle in parallel. WHEN NOT TO USE: Do not use for catalog search (use search_x402_mcp_marketplace) or wallet checks (use get_agent_wallet_status). PARAMETER INTERACTIONS: Set target_tool to a native slug (e.g. 'distill', 'token-intel', 'sec-intel', 'github-audit') or external https:// URL, and pass its primary input in input_value. Omit agent_id and tx_hash during your 5 free calls. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: execute_marketplace_tool(target_tool='example')

Input Schema

TableJSON Schema

Name	Required	Description
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.
`input_value`	Yes	Primary input parameter for the target tool (URL, 0x address, ticker, domain, email, repo, or query).
`target_tool`	Yes	Native tool slug (e.g. 'distill', 'token-intel', 'sec-intel', 'github-audit') or external https:// endpoint URL.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, but the description adds substantial context beyond them: the 5-free-call pricing model, $0.001-$0.02 per call, failed calls never charged, 1-hour result caching (<5ms hits), and the payment-required quote flow with top-up link and retry mechanics. It does not spell out the exact shape of the payment-required response, keeping it just short of a 5.

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 and organized under labeled WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS / pricing blocks, so an agent can scan it quickly. It is somewhat long and the agd_pass_ key and free-call details are repeated between the prose and the schema descriptions, which is mild redundancy rather than bloat.

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 proxy-execution tool with four parameters and an output schema (so return values need not be described), the description covers usage routing, payment lifecycle, caching, error semantics, and retry path. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds genuine interaction semantics: target_tool accepts either a native slug (with examples) or an https:// URL, input_value carries the target's primary input, and agent_id/tx_hash should be omitted during the free trial and supplied on retry. This meaningfully exceeds what the schema descriptions convey.

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 ('Execute') plus the resource (16 native AgentDiet B2A tools by slug, or a proxied external marketplace tool URL), and immediately differentiates itself from sibling tools. An agent can tell exactly what this does without opening the schema.

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?

Contains explicit WHEN TO USE (single tool discovered via search_x402_mcp_marketplace), WHEN NOT TO USE (no catalog search, no wallet checks), and names the alternative for each excluded case plus execute_workflow_bundle for parallel bundles. Nothing is left to inference.

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

All AgentDiet Universal A2A & MCP Tool Discovery, Safe-Proxy & Swarm Router 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?