Skip to main content
Glama

Transfer workspace ownership

transfer_ownership
Destructive

Make the target membership owner and demote yourself to admin. Workspace owners only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "membership_id": "<membership_id>"
    },
    "name": "transfer_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).
membership_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is known. The description adds genuinely non-obvious behavior: the caller is demoted to admin as a side effect, which is exactly the kind of self-affecting consequence an agent needs before invoking. It stops short of saying whether the operation is reversible or what happens to the previous owner's other permissions.

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?

Two short sentences, zero waste, with the effect front-loaded and the permission constraint trailing. Every clause carries information the agent needs.

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?

For a simple two-parameter mutation with no output schema, the definition covers the effect, the self-demotion side effect, and the authorization requirement. Minor gaps remain around the previous owner's residual state and how to source membership_id, but nothing essential to correct invocation 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 coverage is 50%: workspace_id is documented in the schema as coming from whoami, while membership_id has no description anywhere. The phrase "the target membership" hints that membership_id identifies the recipient member, but it adds no format or sourcing detail to compensate for the undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource (transfer workspace ownership) and spells out the concrete effect: the target membership becomes owner and the caller is demoted to admin. It is clear enough to act on without opening the schema, though it does not distinguish itself from the sibling set_member_role, which could plausibly achieve a similar-looking change.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Workspace owners only" gives a clear caller-prerequisite, which is useful gating. However, there is no explicit statement of when to use this versus set_member_role or leave_workspace, and no guidance on the precondition that the target must already be a member.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources