Skip to main content
Glama

Agentropolis

by io.agentropolis
OverviewDiscussionsAdmin

Call an x402 listing through the non-custodial pass-through

call_kit

Send a request to a listing's x402 endpoint through Agentropolis and get the seller's raw response back (status, headers, body). Use it only for listings whose search result has buy='relay_x402' (links.call present); for any other listing, call the seller directly using get_kit_manifest. Flow: call without payment, receive HTTP 402 with the seller's payment requirements unchanged, sign a payment with your own wallet to the seller's payTo, then call again with payment_signature (x402 v2) or x_payment (v1). Agentropolis holds no keys or funds, never changes payTo or amount and charges no fee, but a signed payment you pass is forwarded and may be settled by the seller, so real money can move. Limits: seller's own https host only, 256 KB request, 2 MB response, 25 s timeout (longer for slow first-party kits), 20 calls/min per client. Example: {"id":"seenly.seenly-token-preflight","endpoint":"/api/token-preflight","method":"POST","body":{"chain":"base","tokenAddress":"0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed"}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesListing id exactly as returned by search_kits results[].id, e.g. 'seenly.seenly-token-preflight' or 'mcp.io-github-owner-name'.
bodyNoRequest body. An object is sent as JSON; a string is sent as-is with content_type.
queryNoQuery-string parameters to append, e.g. {"q":"news"}.
methodNoHTTP method; defaults to POST when a body is given, else GET.
endpointNoPath (e.g. '/api/script') or full https URL on the seller's own host. Defaults to the listing's primary endpoint.
x_paymentNoSigned X-PAYMENT header value (x402 v1) from your own wallet; forwarded unchanged. Omit on the first call.
content_typeNoContent-Type for a string body, e.g. 'text/plain'. Ignored for object bodies (sent as application/json).
payment_signatureNoSigned PAYMENT-SIGNATURE header value (x402 v2) from your own wallet; forwarded unchanged. Omit on the first call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Request body (object is sent as JSON)"New value: +"Request body. An object is sent as JSON; a string is sent as-is with content_type."
    • addedInput schema / properties / content_type / description
      Added value: +"Content-Type for a string body, e.g. 'text/plain'. Ignored for object bodies (sent as application/json)."
    • changedInput schema / properties / endpoint / description
      Previous value: -"Path or full https URL on the seller's own host; defaults to the listing's primary endpoint"New value: +"Path (e.g. '/api/script') or full https URL on the seller's own host. Defaults to the listing's primary endpoint."
    • changedInput schema / properties / id / description
      Previous value: -"Listing id from search_kits"New value: +"Listing id exactly as returned by search_kits results[].id, e.g. 'seenly.seenly-token-preflight' or 'mcp.io-github-owner-name'."
    • addedInput schema / properties / id / minLength
      Added value: +3
    • addedInput schema / properties / method / description
      Added value: +"HTTP method; defaults to POST when a body is given, else GET."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Signed PAYMENT-SIGNATURE header value (x402 v2), forwarded unchanged"New value: +"Signed PAYMENT-SIGNATURE header value (x402 v2) from your own wallet; forwarded unchanged. Omit on the first call."
    • addedInput schema / properties / query / description
      Added value: +"Query-string parameters to append, e.g. {\"q\":\"news\"}."
    • changedInput schema / properties / x_payment / description
      Previous value: -"Signed X-PAYMENT header value (x402 v1), forwarded unchanged"New value: +"Signed X-PAYMENT header value (x402 v1) from your own wallet; forwarded unchanged. Omit on the first call."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: states Agentropolis holds no keys or funds, never changes payTo/amount, charges no fee, yet warns 'real money can move' because a signed payment is forwarded and may be settled. Adds concrete limits (https host only, 256 KB request, 2 MB response, 25 s timeout, 20 calls/min) that annotations cannot convey.

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?

Longer than typical but front-loaded and organized into purpose, gating condition, flow, limits, and example. Given the multi-step payment protocol and 8 parameters, the length is largely justified, though the limits and example could be trimmed slightly.

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 high-complexity, non-idempotent, open-world relay tool with no output schema, the description closes the key gaps: it describes the returned payload (status, headers, body), the full auth/payment sequence, and hard limits. 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 protocol-level semantics the schema lacks: the first call is made without payment to elicit the 402, and payment_signature (x402 v2) vs x_payment (v1) are the second-call credentials. The worked example also anchors id/endpoint/method/body usage.

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 ('Send a request to a listing's x402 endpoint ... get the seller's raw response back') and immediately scopes it against siblings by requiring buy='relay_x402' and routing other listings to get_kit_manifest. An agent can distinguish it from get_kit/get_kit_manifest without opening a 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?

Explicit when-to-use ('only for listings whose search result has buy="relay_x402"') and when-not ('for any other listing, call the seller directly using get_kit_manifest'), naming the alternative tool. The two-step 402 flow and payment prerequisites are spelled out rather than 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 Agentropolis toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources