Skip to main content
Glama

initiate_project_transfer

Initiate a project transfer to another wallet. Freezes owner-side mutations until the transfer is accepted, cancelled, or expired.

Instructions

Initiate a two-party project transfer (v1.59+). You must currently own the project (gateway verifies against fresh DB state). Creates a pending row with 72h expiry and freezes owner-side mutations on the project until accepted, cancelled, or expired. The recipient gets the project under the migrate billing policy (project moves into their billing account). Owner's tier lease is NOT refunded. GitHub repo ownership is NOT transferred. Calls POST /projects/v1/:project_id/transfers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject id to transfer. You must currently own it (the gateway verifies against fresh DB state).
to_walletYesRecipient wallet address (any case — the gateway lowercases). Must differ from the current owner.
billing_policyNoBilling policy. Phase 1A supports only `migrate` (default). The project moves into the recipient's billing account.
messageNoOptional free-text note shown to the recipient in the preview and notification emails.
kysigned_record_idNoOptional KySigned record id. Phase 1A stores this verbatim (no verification). Phase 1B will verify against the canonical terms hash.
Behavior5/5

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

With no annotations provided, the description fully bears the burden. It discloses critical traits: 72h expiry, freezing owner-side mutations, no refund of tier lease, no GitHub repo transfer, and the API endpoint. This is comprehensive.

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 well-structured with front-loaded purpose. Each of the 7 sentences adds unique, necessary information (behavior, constraints, endpoint). No wasted words.

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?

Despite no output schema, the description thoroughly explains the effect of the tool: pending row creation, expiry, ownership freeze, billing migration, and what is not transferred. This is sufficient for correct invocation and expectation setting.

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 100% with detailed parameter descriptions. The tool description largely restates this information (e.g., project_id ownership, billing policy) without adding new semantics 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 'Initiate a two-party project transfer' with the specific verb 'initiate' and resource 'project transfer'. It also mentions version requirement (v1.59+) and distinguishes from sibling tools like accept_project_transfer and cancel_project_transfer.

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 description specifies prerequisites ('You must currently own the project') and the resulting behavior (creates pending row, freezes mutations). It does not explicitly mention when not to use or alternatives, 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kychee-com/run402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server