qubic-mcp

remove_network

Remove a saved custom network. Built-in networks like mainnet and testnet cannot be removed. If the active network is removed, it reverts to mainnet.

Instructions

Remove a saved custom network. Cannot remove built-in networks (mainnet, testnet). If the removed network was active, switches back to mainnet.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The name of the custom network to remove

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It clearly states two key behaviors: built-in networks cannot be removed, and if the removed network was active, the tool switches back to mainnet. This goes beyond the basic 'delete' action and helps the agent anticipate side effects.

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 sentences, front-loaded with the action, and no wasted words. The description efficiently covers purpose, a key restriction, and a behavioral consequence in a compact form.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with a single parameter and no output schema, the description is complete. It addresses the main action, the critical edge case (built-in networks), and a relevant fallback behavior (switching to mainnet), covering all necessary context.

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?

The schema fully documents the 'name' parameter (100% coverage), so the baseline is 3. The description adds value by clarifying that the name refers to a 'saved custom network' and that built-in names are invalid, which helps the agent select an appropriate value for the parameter.

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 ('Remove') and resource ('saved custom network'), clearly distinguishing it from sibling tools like add_network, switch_network, and list_networks. It also states what it cannot do (removing built-in networks), further clarifying its scope.

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

Usage Guidelines4/5

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

The description implicitly guides usage by restricting to custom networks and explicitly noting that built-in networks cannot be removed. While it doesn't name alternative tools, the context signals and siblings make it clear when to use this tool. The built-in network exclusion is a useful usage constraint.

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