Skip to main content
Glama
Sign In
ChannelTerm

ChannelTerm

by akira-init1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Resolve File Transfer Cancellation

terminal_resolve_file_transfer_cancel
Destructive

Resolves a file-transfer cancellation confirmation: false resumes the transfer, while true waits for safe cleanup and lease release.

Instructions

Resolve a file-transfer cancellation confirmation; false resumes and true waits for safe cleanup and lease release.

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": {
      "session_id": "<session_id>",
      "request_id": "<request_id>",
      "cancel": "<cancel>"
    },
    "name": "terminal_resolve_file_transfer_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
cancelYesTrue only for an explicit y/Y answer.
request_idYesRequest ID returned by terminal_begin_file_transfer_cancel.
session_idYesActive Session ID or short reference.

Output Schema

NameRequiredDescriptionDefault
stateYes
totalYes
percentYes
transferredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely non-obvious behavior: the false branch resumes the transfer while true blocks for safe cleanup and lease release, which tells the agent what each choice actually causes.

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 core behavior front-loaded and the two branch outcomes packed into one clause. Nothing is wasted or redundant.

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?

With an output schema, full parameter documentation, and destructive/non-idempotent annotations, the description covers what an agent needs about the two outcomes. Minor gap: it does not say what happens if the request_id is stale or expired, a realistic failure mode for a confirmation-resolution tool.

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 100%, so the baseline is 3, and the description earns above it by explaining the consequence of the cancel boolean (resume vs. wait-for-cleanup) — meaning the schema's 'True only for an explicit y/Y answer' does not convey. The session_id and request_id parameters are left entirely to 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 (Resolve) and resource (a file-transfer cancellation confirmation), which is distinct from the sibling terminal_begin_file_transfer_cancel that presumably starts the flow. It is clear what the tool does, though 'resolve a confirmation' is slightly abstract without the accompanying true/false semantics.

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 clause 'false resumes and true waits for safe cleanup and lease release' implicitly frames this as the follow-up step to terminal_begin_file_transfer_cancel, but the description never explicitly states that sequencing or names the alternative. Usage is inferable rather than instructed.

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