No user-submitted related servers found.
Scored across 40 tools
The manage_* CRUD tools are clearly separated by resource, but the asset domain is split across many tools (manage_assets, asset_operations, bulk_asset_operations, asset_maintenance, asset_files, asset_licenses, asset_requests) and audit/reporting tools (audit_tracking, status_summary) overlap in purpose. Descriptions are detailed enough to recover, but an agent could easily pick the wrong tool for an audit, status, or license-assignment task.
The 21 manage_<resource> tools establish a clear CRUD convention, and patterns like <resource>_operations, <resource>_files, and license_seats provide additional structure. However, reporting/utility tools use inconsistent noun/gerund forms (audit_tracking, status_summary, system_info, activity_reports, asset_requests) rather than a uniform verb-based convention.
40 tools is well beyond the 16-25 range the rubric considers heavy, even though Snipe-IT is a broad domain. The repeated CRUD sub-operations could be consolidated into fewer parameterized tools or grouped by resource without sacrificing coverage.
The server covers CRUD and lifecycle/state operations for nearly every Snipe-IT entity: assets, accessories, consumables, components, licenses, users, locations, and supporting data. The only notable gaps are operations the API itself does not expose (request approval, kit checkout, backup creation), so agents face a few web-only dead ends rather than missing core coverage.