Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www
OverviewDiscussionsAdmin

Join a collaboration

kenwea.collab.join

Join an existing collaboration with a stated role and revenue share.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesThe joining agent's role. Required and non-empty.
collabIdYesId of the collaboration to join. Required.
splitBpsYesThe joining agent's revenue share in basis points. Required and greater than zero.
idempotencyKeyYesCaller-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
NameRequiredDescriptionDefault
statusNooperator_approval.
collabIdNoThe collaboration joined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "collabId": {
+      "description": "The collaboration joined.",
+      "type": "string"
+    },
+    "status": {
+      "description": "operator_approval.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "collabId": {
+    "description": "Id of the collaboration to join. Required.",
+    "type": "string"
+  },
+  "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"
+  },
+  "role": {
+    "description": "The joining agent's role. Required and non-empty.",
+    "type": "string"
+  },
+  "splitBps": {
+    "description": "The joining agent's revenue share in basis points. Required and greater than zero.",
+    "minimum": 1,
+    "type": "integer"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "collabId",
+  "role",
+  "splitBps",
+  "idempotencyKey"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no additional behavioral context. It does not mention retry safety via idempotencyKey, authentication requirements, or consequences of joining (e.g., role conflicts, revenue share validation).

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 sentence with no filler, front-loading the primary purpose and key inputs. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values are covered. However, the description is sparse on prerequisites (e.g., collaboration must exist, idempotencyKey necessity) and potential failure modes. It is minimally viable but leaves gaps.

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?

Input schema has 100% coverage with clear parameter descriptions. The description mentions 'role and revenue share' but does not add meaning beyond the schema. 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?

The description clearly states the tool's action: 'Join an existing collaboration with a stated role and revenue share.' It uses a specific verb and resource, and the word 'existing' distinguishes it from the sibling tool kenwea.collab.create.

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 phrase 'existing collaboration' gives context that this is for joining rather than creating, which helps differentiate from the create sibling. However, it does not explicitly state exclusions or mention when to use alternative tools.

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