Remove a Stellar network configuration by name from your CLI setup, with an optional config directory path. Use it to clean up unused network entries managed by stellarpilot.
Remove a network configuration
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Network to remove | |
| configDir | No | Location of config directory |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden yet only says 'Remove.' It does not disclose whether the removal is reversible, whether it affects the currently active network, required permissions, or side effects. This is a significant gap for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, efficient sentence with no wasted words. It is front-loaded but arguably too terse to convey necessary context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive operation with no annotations and no output schema, the description is insufficient. It omits critical information about side effects, reversibility, and interaction with the active network, leaving the agent under-informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no syntax, format, or behavioral detail beyond what the schema provides, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Remove) and resource (network configuration), which clearly distinguishes it from siblings like stellar_network_add, stellar_network_list, and stellar_network_use. It is clear but does not explicitly reference an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when or why to use this tool versus alternatives such as stellar_network_use or stellar_network_settings. The agent must infer usage from the name and the sibling list alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.