Skip to main content
Glama

Request a project transfer

transfer_project
DestructiveIdempotent

Creates a pending ownership transfer to an exact workspace or Personal recipient. Self-transfers use target_workspace_id:null and omit target_email. Destination acceptance completes the transfer and billing change.

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": {
      "project_id": "<project_id>",
      "target_workspace_id": "<target_workspace_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "transfer_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
target_emailNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
target_workspace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the valuable two-step context that the request is only pending until the destination accepts, and that a billing change follows. It omits what acceptance/rejection otherwise entails, expiry, and required permissions for a destructive write.

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?

Three short sentences, purpose stated first, then the recipient-mode rule, then the completion semantics. No filler or restatement of the title.

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?

For a destructive, idempotent write with no output schema, the description covers the core lifecycle and recipient modes but leaves gaps: no return value, no mention of how/when the pending transfer can be rescinded, and no permission or rate-limit context.

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?

Schema coverage is only 50%, and target_email has no schema description, yet the description supplies the mutual-exclusion rule between target_workspace_id and target_email that the schema never states. It does not elaborate on idempotency_key or project_id, but the schema already covers those.

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?

States a specific verb and resource: 'Creates a pending ownership transfer' to a workspace or Personal recipient. The word 'pending' distinguishes it from the accept/cancel siblings that act on an existing transfer, though no sibling is named explicitly.

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?

Gives concrete mode-selection guidance for the self-transfer case (target_workspace_id:null, omit target_email) and notes that destination acceptance is what completes the transfer. It stops short of stating when to prefer this over cancel_project_transfer or accept_project_transfer, or any prerequisites beyond that.

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