Kenwea — Sandbox Attestation & Agent Marketplace

Buy a product version

kenwea.marketplace.purchase

Destructive

Buy a specific product version. THIS SPENDS MONEY from the agent wallet: the wallet must cover the price (insufficient_wallet_balance otherwise; check it with kenwea.wallet.getBalance), and the price counts against the operator's daily budget (budget_exceeded when it would go over). productVersionId is a product VERSION id, not a product id; find it with kenwea.marketplace.search or kenwea.marketplace.preview. A version that has not passed the sandbox is refused with sandbox_not_approved. A price of 1000 USDT or more waits for operator approval and moves no money until then. Returns a LicenseID; to put the product to use, call kenwea.marketplace.install with it.

Input Schema

TableJSON Schema

Name	Required	Description
`license`	No	License to purchase under. Optional; defaults to the license the product version itself declares.
`idempotencyKey`	Yes	Caller-generated unique string that makes this call safe to retry: replaying the same key with the same arguments returns the original result instead of acting twice. Required for this tool. May also be sent as an Idempotency-Key HTTP header; the parameter exists because the MCP tools/call envelope has no way to set headers.
`productVersionId`	Yes	Id of the specific product VERSION being bought -- not the product id. Required.

Output Schema

TableJSON Schema

Name	Required	Description
`Status`	No	Purchase state.
`EscrowID`	No	The escrow holding the funds, where the sale uses one.
`LicenseID`	No	The license minted by the purchase; pass it to kenwea.marketplace.install.
`PurchaseID`	No	The purchase record.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "EscrowID": {
+      "description": "The escrow holding the funds, where the sale uses one.",
+      "type": "string"
+    },
+    "LicenseID": {
+      "description": "The license minted by the purchase; pass it to kenwea.marketplace.install.",
+      "type": "string"
+    },
+    "PurchaseID": {
+      "description": "The purchase record.",
+      "type": "string"
+    },
+    "Status": {
+      "description": "Purchase state.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJul 30, 2026

addedInput schema / properties

Added value: +{
+  "idempotencyKey": {
+    "description": "Caller-generated unique string that makes this call safe to retry: replaying the same key with the same arguments returns the original result instead of acting twice. Required for this tool. May also be sent as an Idempotency-Key HTTP header; the parameter exists because the MCP tools/call envelope has no way to set headers.",
+    "type": "string"
+  },
+  "license": {
+    "description": "License to purchase under. Optional; defaults to the license the product version itself declares.",
+    "type": "string"
+  },
+  "productVersionId": {
+    "description": "Id of the specific product VERSION being bought -- not the product id. Required.",
+    "type": "string"
+  }
+}

addedInput schema / required

Added value: +[
+  "productVersionId",
+  "idempotencyKey"
+]

First observedJul 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare destructiveHint=true/openWorldHint=false, but the description goes well beyond that: it discloses that money moves out of the agent wallet, that spend is charged against the operator's daily budget, that a version failing the sandbox is refused, and that prices >= 1000 USDT are gated on operator approval and move no money until then. That approval-gating detail is exactly the kind of behavior an agent cannot infer from annotations.

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?

The single most consequential fact, that this call spends money, is front-loaded in caps before any mechanics. Every remaining sentence adds a distinct constraint (budget, sandbox, approval threshold, follow-up install) with no padding.

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 3-parameter, destructive, money-spending tool this is complete: prerequisites, failure modes, escalation threshold, and the ignition keyword for the returned LicenseID are all present. An output schema exists, so return-shape detail is appropriately not repeated.

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; the description still adds value by stressing that productVersionId is a VERSION id and by naming the two sibling tools that produce one, which the schema cannot say. It adds less for idempotencyKey/license, but those are already fully documented in the schema.

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 ('Buy a specific product version') and immediately differentiates it from the lookalike siblings: search/preview to find the version id, install to use the result. An agent can place this tool among 27 siblings 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?

Gives explicit when-to-use and preconditions: check wallet balance with kenwea.wallet.getBalance first, obtain productVersionId via kenwea.marketplace.search or preview, then call install afterwards. Failure conditions (insufficient_wallet_balance, budget_exceeded, sandbox_not_approved) are each mapped to the condition that triggers them.

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

All Kenwea — Sandbox Attestation & Agent Marketplace 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.