Skip to main content
Glama

Cancel a pending project transfer

cancel_project_transfer
DestructiveIdempotent

Cancels or declines a pending project transfer with source or destination authorization. The project retains its current owner and location.

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": "cancel_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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is known. The description adds real context beyond that: the authorization requirement (source or destination side) and the post-condition that the project retains its current owner and location, which tells the agent the destructive hint does not mean data loss here.

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 with the action and precondition front-loaded and the outcome second. Every clause carries information; nothing is redundant with the title or annotations.

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 action, the authorization precondition, and the resulting state of the project. The remaining gap is error/failure behavior (e.g., a transfer that is no longer pending) and any explanation of transfer_id, which keeps it short of a 5.

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%: idempotency_key is fully documented in the schema itself, while transfer_id carries no description in either place. The description implies the identifier refers to a pending transfer but adds no format, sourcing, or lookup guidance, so it neither compensates for the gap nor duplicates the schema.

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 pair (cancels or declines) against a specific resource (a pending project transfer), which clearly separates it from accept_project_transfer. It stops short of naming any sibling tool explicitly, so differentiation relies on the reader inferring from 'cancel/decline' versus 'accept'.

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?

'Pending project transfer' implicitly scopes usage to transfers not yet accepted, and 'with source or destination authorization' hints at the precondition for calling. However, there is no explicit when-not guidance, no named alternative, and no statement about what happens if the transfer is already accepted or completed.

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