UAT: `agents tool show` and `agents tool add` output panels missing spec-required `Config` field #4458

New issue

Open

opened 2026-04-08 13:11:00 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-08 13:11:00 +00:00

Owner

Metadata

Milestone: (none — backlog)
Parent Epic: (tool CLI / MCP tool integration)

Bug Report

What Was Tested

The agents tool show and agents tool add CLI command output panels were analyzed against the spec's described output format in docs/specification.md.

Expected Behavior (from spec)

Per docs/specification.md (lines ~7571, ~8325), the agents tool add and agents tool show rich output panels should include a Config: field showing the path to the YAML configuration file used to register the tool:

│ Config: ./tools/run-migrations.yaml          │

The plain-text output format also shows:

Config: ./tools/run-migrations.yaml

And the JSON output format includes:

{
  "config": "./tools/run-migrations.yaml",
  ...
}

Actual Behavior

The _print_tool() function in src/cleveragents/cli/commands/tool.py renders the following fields in the rich panel:

Name, Namespace, Short Name, Description, Source, Type, Timeout, Capability, Resource Slots, Lifecycle

The Config field is completely absent from the output. The Tool domain model (src/cleveragents/domain/models/core/tool.py) has no config_path field, and the as_cli_dict() method does not include a config path. The tool add command reads the config file but does not store its path.

Steps to Reproduce

Create a tool YAML config file (e.g., ./tools/line-counter.yaml)
Run agents tool add --config ./tools/line-counter.yaml
Observe the output panel — no Config: field is shown
Run agents tool show local/line-counter
Observe the output panel — no Config: field is shown

Code Location

src/cleveragents/cli/commands/tool.py — _print_tool() function (line ~80-140): no config field rendered
src/cleveragents/domain/models/core/tool.py — Tool model: no config_path field
src/cleveragents/domain/models/core/tool.py — Tool.as_cli_dict(): no config path included

Impact

Users cannot see which YAML file was used to register a tool, making it difficult to audit, update, or reproduce tool registrations. The spec explicitly shows this field in all output formats (rich, plain, JSON, YAML).

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Metadata - **Milestone**: *(none — backlog)* - **Parent Epic**: *(tool CLI / MCP tool integration)* ## Bug Report ### What Was Tested The `agents tool show` and `agents tool add` CLI command output panels were analyzed against the spec's described output format in `docs/specification.md`. ### Expected Behavior (from spec) Per `docs/specification.md` (lines ~7571, ~8325), the `agents tool add` and `agents tool show` rich output panels should include a `Config:` field showing the path to the YAML configuration file used to register the tool: ``` │ Config: ./tools/run-migrations.yaml │ ``` The plain-text output format also shows: ``` Config: ./tools/run-migrations.yaml ``` And the JSON output format includes: ```json { "config": "./tools/run-migrations.yaml", ... } ``` ### Actual Behavior The `_print_tool()` function in `src/cleveragents/cli/commands/tool.py` renders the following fields in the rich panel: - Name, Namespace, Short Name, Description, Source, Type, Timeout, Capability, Resource Slots, Lifecycle The `Config` field is **completely absent** from the output. The `Tool` domain model (`src/cleveragents/domain/models/core/tool.py`) has no `config_path` field, and the `as_cli_dict()` method does not include a config path. The `tool add` command reads the config file but does not store its path. ### Steps to Reproduce 1. Create a tool YAML config file (e.g., `./tools/line-counter.yaml`) 2. Run `agents tool add --config ./tools/line-counter.yaml` 3. Observe the output panel — no `Config:` field is shown 4. Run `agents tool show local/line-counter` 5. Observe the output panel — no `Config:` field is shown ### Code Location - `src/cleveragents/cli/commands/tool.py` — `_print_tool()` function (line ~80-140): no `config` field rendered - `src/cleveragents/domain/models/core/tool.py` — `Tool` model: no `config_path` field - `src/cleveragents/domain/models/core/tool.py` — `Tool.as_cli_dict()`: no config path included ### Impact Users cannot see which YAML file was used to register a tool, making it difficult to audit, update, or reproduce tool registrations. The spec explicitly shows this field in all output formats (rich, plain, JSON, YAML). --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added this to the v3.5.0 milestone

2026-04-08 17:42:24 +00:00

HAL9000 added the