Move local Stellar configuration to the global directory, centralizing settings for all Stellar CLI operations.
Migrate the local configuration to the global directory
| Name | Required | Description | Default |
|---|---|---|---|
| configDir | No | Location of config directory. By default, it uses $XDG_CONFIG_HOME/stellar if set, falling back to ~/.config/stellar otherwise |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It doesn't say whether migration is destructive, what happens if the global directory already has a config, what gets copied vs moved, whether permissions are required, or whether the operation is reversible. For a mutation tool this is a serious gap.
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?
Single concise sentence, front-loaded with the verb. No waste, though it is minimal to the point of under-specification rather than ideal conciseness.
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 filesystem mutation tool with no annotations and no output schema, the description omits consequences (overwrite behavior, reversibility, failure modes). It is not adequate to invoke safely without additional assumptions.
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 coverage is 100% – the configDir parameter has a full description of default resolution. The tool description adds no parameter detail beyond the schema. Baseline 3 applies when schema fully documents the parameter.
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 verb 'Migrate' and resource 'local configuration', and identifies source/destination ('local' to 'global directory'). However, it doesn't distinguish from sibling stellar_config_dir, which presumably shows the config location, nor do the terms 'local' and 'global' get defined. Purpose is graspable but sibling differentiation is absent.
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 when-to-use guidance, no prerequisites (e.g., whether an existing global config is overwritten), no warnings about irreversible migration. An agent cannot infer when this tool is appropriate vs stellar_config_dir.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.