Skip to main content
Glama

Accept a project transfer

accept_project_transfer
DestructiveIdempotent

Accepts a pending project transfer with destination-owner or administrator authorization. Ownership, access and future billing move to the destination; project IDs and addresses are retained.

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": {
      "transfer_id": "<transfer_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "accept_project_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_idYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag this as destructive and idempotent, and the description adds genuinely useful consequences the annotations cannot express: ownership, access and future billing transfer to the destination, while project IDs and addresses are retained. What is missing is failure behavior and whether the change is reversible, which matters for a destructive mutation.

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?

A single tight sentence with the action front-loaded, followed by authorization and then the side effects. No filler or redundancy.

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 two-parameter mutation with no output schema, the description covers the preconditions, the authorization requirement, and the post-state consequences, which is most of what an agent needs. It falls short only on failure/idempotency recovery behavior and on identifying the source of transfer_id.

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

Parameters2/5

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

Schema coverage is only 50% — transfer_id carries no description at all, and only idempotency_key is documented in the schema. The description never mentions either parameter, so it does nothing to compensate for the undocumented transfer_id or to clarify where the ID comes from (e.g., an invitation or a prior transfer_project call).

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 and resource ('Accepts a pending project transfer') plus the authorization scope, which is enough to tell it apart from cancel_project_transfer and transfer_project by inference. It does not explicitly name those siblings, so differentiation is implied rather than stated.

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?

The phrase 'pending project transfer' implies a precondition (a transfer must already exist and be outstanding) and names required authorization, but there is no explicit guidance on when to choose this over cancel_project_transfer or transfer_project. The agent must infer the workflow position.

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