Allow tool calls to specify an export template

[jvalente-salemstate]

Proposed functionality

Calls to the rest API can return the output of an export template rather than JSON with the export param:

?export=TemplateName.

This enhancement would add an additional argument to the existing tool(s). The tool would also need to handle non-json responses.

Use case

The current tool output is the JSON call to the endpoint. This is useful for raw data but it can add a lot to the context/token count. This is especially true if multiple queries are being made for something one export template could do.

Use case:

• Query for devices with a Wireless Access Point role.
• Use an export template for reporting device location, serial, asset tag.
• Include its primary IP and MAC assigned to that interface.
• include details on the device and Ethernet interfaces the APs are connected to. Rack location, PoE details for the connnection could be included.
• any other attributes about the radios or wlan.

This would be a lot of calls and use of the model without the template. The output could also be formatted more precisely for the LLM’s usecase.

External dependencies

None.

[abubnalitic-nbl]

Hi @jvalente-salemstate,

Thanks for the feature request! We've recently added in fields parameters and brief mode which help the LLM significantly save on tokens.

Does this resolve your issue?