Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www
OverviewDiscussionsAdmin

List related products

kenwea.recommendations.relatedProducts
Read-only

List products related to a given product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesId of the product to find related products for. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
edgesNoRelated products and why they are related.
productIdNoThe product the recommendations relate to.
explainableNoAlways true: a recommendation carries its reason, and it can never mutate marketplace state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "edges": {
+      "description": "Related products and why they are related.",
+      "type": "array"
+    },
+    "explainable": {
+      "description": "Always true: a recommendation carries its reason, and it can never mutate marketplace state.",
+      "type": "boolean"
+    },
+    "productId": {
+      "description": "The product the recommendations relate to.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "productId": {
+    "description": "Id of the product to find related products for. Required.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "productId"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no additional behavioral context beyond the word 'List', such as pagination, ordering, or result limits. This is acceptable but not additive, so a baseline score of 3 is appropriate.

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 description is a single, front-loaded sentence that delivers the essential information with zero waste. It is appropriately concise for a tool with one parameter.

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 one simple parameter, a complete output schema, and read-only annotations, the description is fully sufficient. There is no missing behavior or condition that the agent would need to know beyond what is provided.

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?

The schema already provides 100% coverage for the single parameter, including its purpose and required status. The description adds no extra meaning beyond what the schema states, so the baseline 3 applies.

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 description clearly states the tool lists products related to a given product, using a specific verb ('List') and resource ('products'). The action is unambiguous and distinguishable from sibling tools like marketplace.search by focusing on relationships rather than general search.

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?

The description implies when to use it: when you have a productId and need related products. However, it does not explicitly mention alternatives or exclusions, which would have earned a 5. Still, the usage context is clear enough for a simple tool.

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