Skip to main content
Glama

transfer_organization_ownership

Destructive

Hand a gym to another member (confirm-gated) — owner only and irreversible by the current owner; gym-owned plans move to the new owner. Get explicit confirmation of exactly who becomes the owner before calling with confirm: true.

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": {
      "organizationId": "<organizationId>",
      "newOwnerUserId": "<newOwnerUserId>"
    },
    "name": "transfer_organization_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
newOwnerUserIdYes
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the destructiveHint=true annotation, it adds the irreversibility ('irreversible by the current owner') and the side effect that gym-owned plans transfer to the new owner. It also discloses the confirm-gating so the agent knows an omitted confirm yields only a preview. The one residual gap is whether the previous owner's access changes, but the key behavioral risks are disclosed.

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 sentences, no filler, with the operation, its constraints, and its side effects front-loaded ahead of the call protocol. Every clause carries distinct information.

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?

For a destructive, no-output-schema mutation tool, the description covers reversibility, side effects, permission scope, and the preview/execute distinction. That is everything an agent needs to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema description coverage (confirm is already documented in the schema), the description compensates by explaining what newOwnerUserId should represent — the person who becomes the owner — and by tying confirm to the required human-confirmation step. The two ID parameters remain self-explanatory but unelaborated.

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?

'Hand a gym to another member' is a specific verb+resource that is clearly distinct from sibling role-management tools like assign_organization_member_role. It also states the scope of the effect (gym-owned plans move to the new owner), so an agent knows exactly what operation this is.

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?

It gives explicit preconditions — owner only — and a concrete call protocol: obtain explicit confirmation of exactly who becomes the owner, then call with confirm: true. It stops short of naming an alternative tool to use when the caller lacks ownership, but the context is clear.

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.