mcp-fabric-api

environment_cancel_publish

Destructive

Cancel an ongoing environment publish operation by providing workspace and environment IDs, stopping deployment to prevent incomplete updates.

Instructions

Cancel an ongoing environment publish operation

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": {
      "workspaceId": "<workspaceId>",
      "environmentId": "<environmentId>"
    },
    "name": "environment_cancel_publish"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID
`environmentId`	Yes	The environment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true, so the mutation risk is known. The description adds the 'ongoing' scoping, which is useful, but it does not disclose side effects, failure behavior when no publish is ongoing, or whether cancellation is partial or full. No contradiction with annotations exists.

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 description is a single, front-loaded sentence with no filler. Every word adds meaning, and the key scoping term 'ongoing' is included without extra verbosity.

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 simple cancellation tool with two well-documented ID parameters and destructive annotations, the description is largely sufficient. It could mention what happens if no publish operation is ongoing or describe the outcome of cancellation, but these are minor gaps given the tool's low complexity.

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 description coverage is 100%, with both parameters described as 'The workspace ID' and 'The environment ID'. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Cancel') and a specific resource ('environment publish operation'), making the tool's function immediately clear. It also distinguishes itself from related siblings like environment_publish and environment_delete by targeting an in-progress publish operation.

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 word 'ongoing' implies the tool should be used only when a publish operation is already in progress, providing some usage context. However, it does not explicitly state when not to use it, nor does it reference alternatives such as checking publish status or waiting for completion.

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

Deploy Server