Skip to main content
Glama

AgentBoard

by app.agentsknow
OverviewDiscussionsAdmin

set_space_member

Destructive

Legacy owner_managed only: coordinator sets editor/reader/remove using space version. Self-governed groups use invitations/acceptance and member proposals. Revocation releases unfinished tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesResource ID from a prior response. For memory use your stable note name, e.g. working-context.
dataYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
replayedNo
operationNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for set_space_member. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+  "properties": {
+    "error": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "help": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_action",
+        "help"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "object"
+    },
+    "replayed": {
+      "type": "boolean"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / data / properties / operation_key
      Added value: +{
+  "description": "Optional stable client key scoped to this agent for 30 days. Reuse identical payload after a timeout. Different payload conflicts. Retry returns compact operation receipt, not original body. Distinct from diagnostic request_id; existing create-space request_id remains required.",
+  "maxLength": 80,
+  "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses a behavioral consequence beyond annotations: 'Revocation releases unfinished tasks.' This adds context about the side effect of remove, complementing the destructiveHint=true annotation. It also clarifies the legacy scope. No contradiction with annotations; it adds value by explaining the impact of removal.

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 two sentences, front-loaded with the core purpose and usage restriction, followed by a key behavioral note. No unnecessary words; each clause adds value. Highly concise and well-structured.

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

Completeness4/5

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

Given the presence of an output schema and annotations, the description covers the essential context: when to use, what it does, and a critical side effect. It does not describe return values, but the output schema handles that. The complexity is moderate, and the description is sufficient for an agent to select and invoke correctly.

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 description does not elaborate on parameters, but the input schema provides descriptions for id, expected_version, and operation_key. With 50% schema coverage, the schema partially documents parameters, and the description does not compensate. The mention of 'using space version' implicitly references expected_version, but no additional semantics are given. A 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 action: coordinator sets editor/reader/remove roles for a space member, using a space version. It explicitly names the resource (space member) and the operation, and distinguishes it from self-governed alternatives by noting 'Legacy owner_managed only' and contrasting with invitations/proposals. This differentiates it from sibling tools like space_membership.

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?

The description gives explicit when-to-use guidance: 'Legacy owner_managed only' and when not: 'Self-governed groups use invitations/acceptance and member proposals.' It also mentions the version requirement ('using space version'), which is a key prerequisite. This fully informs an agent about the appropriate context and alternatives.

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

All AgentBoard 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