Kenwea — Sandbox Attestation & Agent Marketplace

Install a purchased product

kenwea.marketplace.install

Install a product this agent has bought. licenseId is the LicenseID kenwea.marketplace.purchase returned; runtime is optional, and if the product's manifest requires a different runtime the call fails with compatibility_failed (runtime_mismatch) and installs nothing. Fails with license_required when the license is not active or not yours. Spends nothing and returns an InstallationID. Repeating the call with the same idempotencyKey returns the same installation; a new key records another one.

Input Schema

TableJSON Schema

Name	Required	Description
`runtime`	No	Runtime the artifact will be installed into. Optional, but if the product manifest declares a required runtime, a mismatch fails with compatibility_failed / runtime_mismatch rather than installing.
`licenseId`	Yes	Id of a license this agent already owns, from a completed purchase. Required.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`InstallationID`	No	The installation record.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "InstallationID": {
+      "description": "The installation record.",
+      "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"
+  },
+  "licenseId": {
+    "description": "Id of a license this agent already owns, from a completed purchase. Required.",
+    "type": "string"
+  },
+  "runtime": {
+    "description": "Runtime the artifact will be installed into. Optional, but if the product manifest declares a required runtime, a mismatch fails with compatibility_failed / runtime_mismatch rather than installing.",
+    "type": "string"
+  }
+}

addedInput schema / required

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

First observedJul 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds substantial context beyond them: the exact failure modes (compatibility_failed / runtime_mismatch, license_required), the guarantee that a failed call installs nothing and that the call spends no money, and the return value. This is rich disclosure rather than restating annotations.

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?

The sentence order is well front-loaded (what it does, then inputs, then failure modes, then cost/return, then idempotency). It is dense but each clause carries information; the idempotency sentence is slightly long, keeping it from a full 5.

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?

With an output schema present, return values need not be explained, yet the description still notes the InstallationID. Combined with error taxonomy, cost behavior, and retry semantics, nothing an agent needs to invoke this correctly is missing.

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 100%, so the schema already documents all three parameters in detail, including the runtime mismatch semantics and the idempotencyKey retry behavior. The description's only marginal addition is naming kenwea.marketplace.purchase as the source of licenseId; otherwise it restates what the schema provides, so the baseline 3 is appropriate.

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?

A specific verb+resource ('Install a product this agent has bought') that clearly distinguishes it from the sibling marketplace operations (purchase, preview, publish, search). The description also names the prerequisite license source, so an agent knows exactly which action this is.

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?

It establishes when to use it (after a completed purchase, with an owned licenseId) and implicitly routes the agent away from purchase by tying licenseId to that tool's output. It never explicitly states when NOT to use it or names preview/publish as alternatives, so it falls short of a full 5.

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.