Genomics MCP

Official

by rewire-bio

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

cancel_transfer

Stop an active genomic data transfer using its transfer ID, halting progress when a running job is no longer needed.

Instructions

Cancel a running transfer. Available for: default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`transfer_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`error`	No	Set when status is error.
`errors`	No	Per-source failures in partial results.
`limits`	No
`status`	Yes
`warnings`	No
`operation`	Yes
`provenance`	No
`truncation`	No
`source_status`	No
`schema_version`	No		1
`metadata_omitted`	No	Entries dropped from provenance/source_status/errors/warnings (or text shortened) to fit max_response_bytes. Absent when metadata is complete.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 28, 2026

addedOutput schema / properties / metadata_omitted

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "integer"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Entries dropped from provenance/source_status/errors/warnings (or text shortened) to fit max_response_bytes. Absent when metadata is complete.",
+  "title": "Metadata Omitted"
+}

First observedv0.1.0Sep 24, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare a non-read-only, open-world, non-destructive mutation. The description adds the useful 'running' state constraint, but omits auth needs, reversibility, side effects, and what cancellation does to the underlying transfer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines with the core purpose front-loaded and no wasted prose. The second line, 'Available for: default', is vague and does not clearly earn its place.

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?

The tool is simple, annotations cover its safety profile, and an output schema exists, so the description need not explain return values. Still, it omits usage guidance and any transfer_id semantics, leaving the agent to infer key calling details.

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 description coverage is 0% and the single required transfer_id has no schema description. The description adds no format, source, or qualifier for transfer_id, so it does not compensate for the gap, though the param name is fairly self-explanatory.

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?

States a specific verb ('Cancel') and resource ('transfer') with the state constraint 'running'. It does not explicitly differentiate from siblings such as get_transfer_status, though no sibling performs cancellation, so it is clear but not fully sibling-routing.

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?

Provides no when-to-use guidance, prerequisites, or alternatives. 'Available for: default' is cryptic and does not explain when an agent should choose cancellation versus 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.