get_configs MCP tool: filtering by config_id or branch_id not supported

[beckavac]

Bug description

The get_configs MCP tool does not accept config_id or branch_id as input parameters, making it impossible to fetch a specific configuration from a specific branch. Passing these parameters causes a validation error.

Steps to reproduce

kbagent --json tool call get_configs --project slevomat \
  --input '{"config_id": "746772863", "branch_id": "1285731"}'

Response:

Found 2 validation error(s) for call[get_configs]
errors:
- field: config_id
  message: Unexpected keyword argument
- field: branch_id
  message: Unexpected keyword argument

Expected behavior

get_configs should support:

• config_id — to fetch a single specific configuration instead of all configs
• branch_id — to fetch from a specific dev branch (currently always uses the project's active branch)

Actual behavior

Both parameters are rejected as unexpected. The tool always returns ALL configurations for the active branch, with no filtering option.

Workaround used

Direct Keboola Storage REST API call:

curl -H "X-StorageApi-Token: $TOKEN" \
  "https://connection.keboola.com/v2/storage/branch/1285731/components/keboola.snowflake-transformation/configs/746772863"

Impact

• AI agents cannot efficiently fetch a single config — they must download all configs and filter locally
• Branch override is impossible via MCP tools; must use raw API
• Breaks the agent workflow when working across multiple branches

Suggestion

Add optional parameters to get_configs:

• config_id: string — return only this specific configuration
• branch_id: string — override the active branch for this read

Context

• kbagent version: 0.9.0
• Project: Slevomat (226), dev branch: 1285731
• Use case: reading Products SQL (config 746772863) from dev branch during SQL optimization task

[padak]

Thanks for reporting this! The root cause was misleading documentation -- the MCP tool get_configs works correctly, but our docs showed a wrong example (get_config with flat config_id) and didn't clarify that branch_id is a CLI flag (--branch), not a tool input parameter.

Fixed in PR #70:

• Corrected get_configs example with proper configs list format
• Added "Discovering tool parameters" section (how to inspect inputSchema)
• Added explicit warning that --branch is a CLI flag, not a tool input param
• Updated kbagent context and gotchas docs

Correct usage:

# Get specific config from a dev branch
kbagent --json tool call get_configs --project slevomat --branch 1285731 \
  --input '{"configs": [{"component_id": "keboola.snowflake-transformation", "configuration_id": "746772863"}]}'

# Discover accepted parameters for any tool
kbagent --json tool list | jq '.data.tools[] | select(.name == "get_configs") | .inputSchema'