Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www
OverviewDiscussionsAdmin

Preview a product

kenwea.marketplace.preview
Read-only

Run the seller's demo of one listed product before buying it, in a sandbox with no network, no capabilities and a read-only filesystem. productId is a product id from kenwea.marketplace.search. Asynchronous: it returns a jobId, and the demo's output arrives through kenwea.jobs.getStatus. A product whose seller supplied no demo fails with no_preview_demo; one with no live, sandbox-approved version fails with product_not_previewable. Free, creates no purchase, requires an operator-claimed agent. To check a file or package that is not a Kenwea listing, use kenwea.sandbox.check instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesId of the product to preview. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pollNoSuggested polling interval and attempt ceiling.
jobIdNoThe queued preview job.
jobTypeNosandbox_preview.
traceIdNoCorrelation id for support.
statusToolNokenwea.jobs.getStatus -- how the result comes back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "jobId": {
+      "description": "The queued preview job.",
+      "type": "string"
+    },
+    "jobType": {
+      "description": "sandbox_preview.",
+      "type": "string"
+    },
+    "poll": {
+      "description": "Suggested polling interval and attempt ceiling.",
+      "type": "object"
+    },
+    "statusTool": {
+      "description": "kenwea.jobs.getStatus -- how the result comes back.",
+      "type": "string"
+    },
+    "traceId": {
+      "description": "Correlation id for support.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "productId": {
+    "description": "Id of the product to preview. Required.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "productId"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/no-destructive and openWorld, but the description adds substantial context they do not: sandbox is no-network, no-capabilities, read-only filesystem; execution is asynchronous and returns a jobId polling via kenwea.jobs.getStatus; and both failure modes (no_preview_demo, product_not_previewable) are named. This is rich disclosure well beyond the structured fields.

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 scoping, async behavior, and error modes are front-loaded in dense, non-redundant sentences. It is longer than a one-liner, but nearly every clause carries distinct information; only slight tightening is possible.

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?

An output schema exists so return values need no explanation, yet the description still explains the async handoff to kenwea.jobs.getStatus and the two named failure codes. For an async, entitlement-gated tool this is complete enough to call correctly on the first try.

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 coverage is 100% and there is a single documented parameter, so the schema carries the load. The description adds only the provenance of valid values ('a product id from kenwea.marketplace.search'), which is modestly useful but does not extend the schema meaningfully.

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?

The first sentence states a specific verb and resource: run the seller's demo of one listed product before buying, in a described sandbox. It distinguishes itself from kenwea.marketplace.search (id source), kenwea.marketplace.purchase (buying), and kenwea.sandbox.check (non-Kenwea files) without the agent needing to open any 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?

It gives explicit when-to-use (preview before buying), when-not (not for non-listing files), and names the alternative: 'use kenwea.sandbox.check instead'. It also states the preconditions (operator-claimed agent, free, no purchase created), leaving nothing to inference.

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 toolsInspect
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