Retrieve Stellar CLI version details to verify installed software or output only the full or major version number when needed.
Print version information for the Stellar CLI
| Name | Required | Description | Default |
|---|---|---|---|
| onlyVersion | No | Print only the version number | |
| onlyVersionMajor | No | Print only the major version number |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It only says 'Print version information' and omits output format, side effects, authentication needs, or any other behavioral context. For a read-only informational command this is minimal and leaves significant gaps.
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 front-loaded sentence with zero filler. Every word earns its place and the purpose is immediately clear.
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?
The tool is simple with two optional booleans and no output schema. The description states the purpose but does not describe output format or behavioral variations, leaving some gaps for the agent to infer from parameter names.
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 both boolean parameters are fully documented in the schema itself. The description adds no parameter details, making the baseline score of 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 ('Print') and resource ('version information for the Stellar CLI'), which is clear and distinguishable from siblings like stellar_config_dir or stellar_doctor. No explicit sibling differentiation, but none is needed for this unique command.
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?
The description provides no when-to-use guidance, no alternatives, and no conditions. It only restates the action, leaving the agent to infer that this is the command for retrieving the CLI version.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.