qubic-mcp

add_network

Add a custom Qubic network by specifying a name and RPC URL, optionally an API endpoint, to save it for later connection.

Instructions

Save a custom Qubic network (e.g., a local lite node). Stored in ~/.qubic-mcp/networks.json. Use switch_network to activate it.

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

Input Schema

Name	Required	Description
`name`	Yes	A friendly name for this network (e.g., "local", "dev-node", "my-lite")
`apiUrl`	No	Optional separate API/query endpoint. Defaults to the RPC URL if not provided.
`rpcUrl`	Yes	The RPC endpoint URL (e.g., "http://192.168.1.50:21841")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing side effects. It discloses the persistence path (~/.qubic-mcp/networks.json) and implies the network is not activated immediately. However, it does not mention overwrite behavior, validation, or failure conditions, leaving some behavioral aspects undisclosed.

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 two sentences, front-loaded with the primary purpose, and includes only essential information (storage location and activation follow-up). Every word earns its place with no redundancy.

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 tool with 3 parameters and no output schema, the description covers the core aspects: what it does, where it persists, and the required next step (activation). It does not mention duplicate handling or success/failure responses, but given the tool's simplicity, this is adequate and slightly above the minimum viable.

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?

The schema provides 100% documentation of all three parameters, so the baseline is 3. The description adds minimal semantic value beyond the schema—it gives an example of a name and the storage purpose, but does not explain parameter relationships or constraints not already in the schema.

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 ('Save') and resource ('custom Qubic network'), provides a concrete example ('local lite node'), and clearly distinguishes it from sibling tools by noting that activation is handled by switch_network. This leaves no ambiguity about what the tool does.

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 states the storage location and explicitly directs the user to use switch_network to activate the saved network, providing clear context for when to use this tool. It does not include explicit exclusions (e.g., duplicate handling), but the guidance is sufficient for a simple add operation.

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