List saved environments from ~/.bowire/environments.json—names, server URLs, and variables—so agents can inspect available API targets before calls.
List Bowire environments stored under ~/.bowire/environments.json — names, server URLs, variables.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does 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 usefully discloses the storage location and return fields, but does not state that the operation is read-only, whether authentication or permissions are needed, or any pagination or failure behavior.
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?
The description is a single front-loaded sentence with no redundant or filler text. Every clause earns its place by naming the resource, storage path, and returned data.
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?
With no annotations, no parameters, and no output schema, the description provides the essential resource scope and return fields. It could add a brief note on read-only behavior or authentication needs, but for a simple list tool it is largely complete.
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?
The tool has zero parameters, so the schema is empty and the baseline is 4. The description correctly does not invent parameter semantics, and its mention of returned fields is separate from parameter meaning.
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?
The description uses a specific verb ('List'), a precise resource ('Bowire environments'), and names the returned fields (names, server URLs, variables). It is clearly distinct from sibling list/show tools such as bowire.mock.list or bowire.record.list because it scopes to environments.
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 implies its usage by stating what it lists, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. For a zero-parameter list tool this is minimally adequate, though an agent receives no routing help.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.