Search catalog platforms by port demand
catalog_search_platformsFind published platforms that can serve a port demand (for example 60×100G plus 4×400G for a data-center top-of-rack switch), closest fit first: fewest spare ports, then fewest rack units, then least capacity headroom. Each result explains the fit and lists caveats (breakout cables, a non-default port mode, port-pairing rules) that you should pass on to the user. Also reports how many platforms of the use case meet the demand, how many could not be evaluated, and the nearest misses when nothing fits. Answers carry catalog_url (the public catalog page) and build_bom_url (Open in SKUit to build a full bill of materials; the builder requires a SKUit account).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"use_case_id": "<use_case_id>",
"port_requirements": "<port_requirements>"
},
"name": "catalog_search_platforms"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many results (default 5, max 10). | |
| vendors | No | Only these vendors. Case-insensitive, on whole words: "Juniper" matches "Juniper Networks". An unknown name is reported back with the vendors that do have platforms for the use case. | |
| form_factor | No | Only this form factor, e.g. "fixed" or "modular". | |
| use_case_id | Yes | Deployment role: "campus-access" (Campus access layer), "dc-tor" (ToR & Leaf), "dc-core" (DC core / spine), "wan-edge" (WAN edge / branch), "smb" (SMB / small campus), "campus-dist" (Campus distribution), "load-balancer" (Security Appliances), "ai-fabric" (AI fabric). | |
| poe_required | No | Only platforms that supply PoE. | |
| max_rack_units | No | Only platforms at most this many rack units tall. | |
| port_requirements | Yes | The ports needed, one row per speed. |