Skip to main content
Glama
Sign In
Colab MCP

Colab MCP

by ALiwoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cancel_transfer

Cancels an active file transfer and deletes its incomplete temporary files when the connection is still available.

Instructions

Cancel a file transfer and remove its incomplete temporary files where the connection is still available.

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>"
    },
    "name": "cancel_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

Beyond the readOnlyHint=false annotation, the description adds important behavior: it removes incomplete temporary files and the cleanup depends on connection availability. However, it does not state whether cancellation is irreversible, what happens if the transfer is already complete, or what permissions are required.

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 definition is a single front-loaded sentence with no wasted wording. The primary action and secondary cleanup behavior are stated compactly.

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 simple one-parameter mutation tool with no output schema, the description covers the main action and an important side effect. It is still incomplete because it does not explain the required transfer_id, failure modes, or return behavior.

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?

The input schema has 0% description coverage, so the description must compensate for the undocumented transfer_id parameter. It only implies that the parameter identifies a file transfer and gives no format, source, or usage detail.

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: it cancels a file transfer and removes incomplete temporary files. This clearly separates it from status/list tools, though it does not explicitly name sibling alternatives such as transfer_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to cancel a transfer, but provides no explicit when-to-use guidance, prerequisites, or comparison with alternatives like checking transfer_status first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools