personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Diagnostic] cmdb-assistant: Incomplete parameter schemas for update operations #137

New Issue
Closed
opened 2026-01-24 17:07:07 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-24 17:07:07 +00:00
Owner
Copy Link

Diagnostic Report

Generated: 2026-01-24T17:03:00Z
Command Tested: cmdb-assistant NetBox MCP plugin update operations
Reporter: Claude Code via /debug-report

Project Context

Field Value
Repository bandit-den/serv-home-apps
Git Remote ssh://git@hotserv.tailc9b278.ts.net:2222/bandit-den/serv-home-apps.git
Working Directory /home/lmiranda/apps-home
Current Branch main

Issue Summary

The cmdb-assistant NetBox MCP plugin has incomplete parameter schemas for update operations. The virt_update_vm and virt_update_cluster tools only expose the id parameter in their schemas, but don't include updatable fields like description, comments, vcpus, memory, disk.

This forces users to bypass the MCP tools and call the NetBox API directly using curl/Python scripts.

Detailed Findings

Tool: virt_update_vm

Schema returned by ToolSearch:

{
  "properties": {
    "id": {"description": "VM ID", "type": "integer"}
  },
  "required": ["id"]
}

Expected fields (based on NetBox API):

  • id (required) - VM ID
  • description (optional) - VM description
  • comments (optional) - Detailed comments/notes
  • vcpus (optional) - Number of vCPUs
  • memory (optional) - Memory in MB
  • disk (optional) - Disk in GB
  • status (optional) - VM status
  • role (optional) - Device role ID
  • platform (optional) - Platform ID
  • cluster (optional) - Cluster ID

Impact: Cannot update VM metadata through MCP tools.

Tool: virt_update_cluster

Schema returned by ToolSearch:

{
  "properties": {
    "id": {"description": "Cluster ID", "type": "integer"}
  },
  "required": ["id"]
}

Expected fields (based on NetBox API):

  • id (required) - Cluster ID
  • name (optional) - Cluster name
  • description (optional) - Cluster description
  • comments (optional) - Detailed comments/notes
  • type (optional) - Cluster type ID
  • site (optional) - Site ID
  • status (optional) - Cluster status

Impact: Cannot update cluster metadata through MCP tools.

Diagnostic Results

Test 1: validate_repo_org

Call: validate_repo_org(repo="bandit-den/serv-home-apps")
Status: PASS
Response:

{
  "is_organization": false
}

Test 2: get_labels

Call: get_labels(repo="bandit-den/serv-home-apps")
Status: FAIL
Response:

Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/labels

Test 3: list_issues

Call: list_issues(repo="bandit-den/serv-home-apps", state="open")
Status: FAIL
Response:

Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/issues?state=open

Test 4: list_milestones

Call: list_milestones(repo="bandit-den/serv-home-apps")
Status: FAIL
Response:

Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/milestones?state=open

Test 5: suggest_labels

Call: suggest_labels(context="Bug fix: cmdb-assistant NetBox MCP plugin...", repo="personal-projects/leo-claude-mktplace")
Status: PASS (but returned empty array)
Response:

[]

Summary

  • Total Tests: 5
  • Passed: 2
  • Failed: 3

Failed Tools

  1. get_labels: 404 Not Found - Repository doesn't exist or has no labels configured
  2. list_issues: 404 Not Found - Repository doesn't exist or has no issues
  3. list_milestones: 404 Not Found - Repository doesn't exist or has no milestones

Note: The 404 errors for tests 2-4 are expected because bandit-den/serv-home-apps is a new repository with no issues/milestones yet. These are not bugs.

Error Category

  • Parameter Format - Missing parameters in MCP tool schemas
  • Authentication
  • Not Found (expected for new repo)
  • Network
  • Logic

Hypothesis

The cmdb-assistant plugin's MCP tool definitions are incomplete for update operations. The Python code likely implements the full NetBox API functionality, but the MCP tool schema definitions (in tools.py or similar) only expose the id parameter.

This is a documentation/schema definition issue, not a functional code issue.

Suggested Investigation

  1. File: plugins/cmdb-assistant/server/tools.py (or equivalent)

    • Check the tool definitions for virt_update_vm and virt_update_cluster
    • Compare with the NetBox API documentation for these endpoints
    • Add all updatable fields to the tool parameter schemas

  2. File: plugins/cmdb-assistant/server/netbox_client.py (or equivalent)

    • Verify that the underlying Python functions support these parameters
    • If not, implement parameter passing from MCP tools to NetBox API

  3. Similar tools to check:

    • dcim_update_device - likely has same issue
    • dcim_update_site - likely has same issue
    • Any other *_update_* tools in the plugin

Reproduction Steps

  1. Navigate to /home/lmiranda/apps-home
  2. Use ToolSearch to find mcp__plugin_cmdb-assistant_netbox__virt_update_vm
  3. Observe that schema only shows id parameter
  4. Attempt to update VM description/comments - not possible through MCP tool
  5. Must resort to direct NetBox API calls via curl/Python

Workaround Used

Created Python script to call NetBox API directly:

import requests
NETBOX_URL = "https://netbox.hotserv.cloud"
NETBOX_TOKEN = "..."
update_payload = {
    "description": "...",
    "comments": "...",
    "vcpus": 1,
    "memory": 512,
    "disk": 10
}
url = f"{NETBOX_URL}/api/virtualization/virtual-machines/{vm_id}/"
response = requests.patch(url, headers=headers, json=update_payload)

Generated by /debug-report

## Diagnostic Report **Generated**: 2026-01-24T17:03:00Z **Command Tested**: cmdb-assistant NetBox MCP plugin update operations **Reporter**: Claude Code via /debug-report ## Project Context | Field | Value | |-------|-------| | Repository | `bandit-den/serv-home-apps` | | Git Remote | `ssh://git@hotserv.tailc9b278.ts.net:2222/bandit-den/serv-home-apps.git` | | Working Directory | `/home/lmiranda/apps-home` | | Current Branch | `main` | ## Issue Summary The cmdb-assistant NetBox MCP plugin has incomplete parameter schemas for update operations. The `virt_update_vm` and `virt_update_cluster` tools only expose the `id` parameter in their schemas, but don't include updatable fields like `description`, `comments`, `vcpus`, `memory`, `disk`. This forces users to bypass the MCP tools and call the NetBox API directly using curl/Python scripts. ## Detailed Findings ### Tool: virt_update_vm **Schema returned by ToolSearch**: ```json { "properties": { "id": {"description": "VM ID", "type": "integer"} }, "required": ["id"] } ``` **Expected fields** (based on NetBox API): - `id` (required) - VM ID - `description` (optional) - VM description - `comments` (optional) - Detailed comments/notes - `vcpus` (optional) - Number of vCPUs - `memory` (optional) - Memory in MB - `disk` (optional) - Disk in GB - `status` (optional) - VM status - `role` (optional) - Device role ID - `platform` (optional) - Platform ID - `cluster` (optional) - Cluster ID **Impact**: Cannot update VM metadata through MCP tools. ### Tool: virt_update_cluster **Schema returned by ToolSearch**: ```json { "properties": { "id": {"description": "Cluster ID", "type": "integer"} }, "required": ["id"] } ``` **Expected fields** (based on NetBox API): - `id` (required) - Cluster ID - `name` (optional) - Cluster name - `description` (optional) - Cluster description - `comments` (optional) - Detailed comments/notes - `type` (optional) - Cluster type ID - `site` (optional) - Site ID - `status` (optional) - Cluster status **Impact**: Cannot update cluster metadata through MCP tools. ## Diagnostic Results ### Test 1: validate_repo_org **Call**: `validate_repo_org(repo="bandit-den/serv-home-apps")` **Status**: PASS **Response**: ```json { "is_organization": false } ``` ### Test 2: get_labels **Call**: `get_labels(repo="bandit-den/serv-home-apps")` **Status**: FAIL **Response**: ``` Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/labels ``` ### Test 3: list_issues **Call**: `list_issues(repo="bandit-den/serv-home-apps", state="open")` **Status**: FAIL **Response**: ``` Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/issues?state=open ``` ### Test 4: list_milestones **Call**: `list_milestones(repo="bandit-den/serv-home-apps")` **Status**: FAIL **Response**: ``` Error: 404 Client Error: Not Found for url: https://gitea.hotserv.cloud/repos/bandit-den/serv-home-apps/milestones?state=open ``` ### Test 5: suggest_labels **Call**: `suggest_labels(context="Bug fix: cmdb-assistant NetBox MCP plugin...", repo="personal-projects/leo-claude-mktplace")` **Status**: PASS (but returned empty array) **Response**: ```json [] ``` ## Summary - **Total Tests**: 5 - **Passed**: 2 - **Failed**: 3 ### Failed Tools 1. **get_labels**: 404 Not Found - Repository doesn't exist or has no labels configured 2. **list_issues**: 404 Not Found - Repository doesn't exist or has no issues 3. **list_milestones**: 404 Not Found - Repository doesn't exist or has no milestones **Note**: The 404 errors for tests 2-4 are expected because `bandit-den/serv-home-apps` is a new repository with no issues/milestones yet. These are not bugs. ### Error Category - [x] Parameter Format - Missing parameters in MCP tool schemas - [ ] Authentication - [ ] Not Found (expected for new repo) - [ ] Network - [ ] Logic ### Hypothesis The cmdb-assistant plugin's MCP tool definitions are incomplete for update operations. The Python code likely implements the full NetBox API functionality, but the MCP tool schema definitions (in `tools.py` or similar) only expose the `id` parameter. This is a **documentation/schema definition issue**, not a functional code issue. ### Suggested Investigation 1. **File**: `plugins/cmdb-assistant/server/tools.py` (or equivalent) - Check the tool definitions for `virt_update_vm` and `virt_update_cluster` - Compare with the NetBox API documentation for these endpoints - Add all updatable fields to the tool parameter schemas 2. **File**: `plugins/cmdb-assistant/server/netbox_client.py` (or equivalent) - Verify that the underlying Python functions support these parameters - If not, implement parameter passing from MCP tools to NetBox API 3. **Similar tools to check**: - `dcim_update_device` - likely has same issue - `dcim_update_site` - likely has same issue - Any other `*_update_*` tools in the plugin ## Reproduction Steps 1. Navigate to `/home/lmiranda/apps-home` 2. Use `ToolSearch` to find `mcp__plugin_cmdb-assistant_netbox__virt_update_vm` 3. Observe that schema only shows `id` parameter 4. Attempt to update VM description/comments - not possible through MCP tool 5. Must resort to direct NetBox API calls via curl/Python ## Workaround Used Created Python script to call NetBox API directly: ```python import requests NETBOX_URL = "https://netbox.hotserv.cloud" NETBOX_TOKEN = "..." update_payload = { "description": "...", "comments": "...", "vcpus": 1, "memory": 512, "disk": 10 } url = f"{NETBOX_URL}/api/virtualization/virtual-machines/{vm_id}/" response = requests.patch(url, headers=headers, json=update_payload) ``` --- *Generated by /debug-report*
lmiranda added the Component/APITech/Python labels 2026-01-24 17:08:35 +00:00
lmiranda commented 2026-01-24 17:19:46 +00:00
Author
Owner
Copy Link

Fix proposed in PR #138

Changes:

  • Expanded MCP tool schemas for 15 update operations (virtualization, dcim, ipam)
  • Each tool now exposes all commonly-used optional fields matching the NetBox API
  • No functional code changes - only schema metadata additions

To test after merge:

  1. Reinstall/update the plugin
  2. Run ToolSearch for virt_update_vm - verify new fields appear in schema
  3. Test updating a VM with description or comments fields

Please test after merge and report back.

Fix proposed in PR #138 **Changes:** - Expanded MCP tool schemas for 15 update operations (virtualization, dcim, ipam) - Each tool now exposes all commonly-used optional fields matching the NetBox API - No functional code changes - only schema metadata additions **To test after merge:** 1. Reinstall/update the plugin 2. Run `ToolSearch` for `virt_update_vm` - verify new fields appear in schema 3. Test updating a VM with `description` or `comments` fields Please test after merge and report back.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/API Tech/Python
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?