Skip to main content
Glama
jillesca

gNMIBuddy

by jillesca

get_device_profile_api

Retrieve a device profile that identifies its service provider role and key protocol features, enabling context-aware automation and troubleshooting in gNMI-monitored networks.

Instructions

Retrieve a comprehensive device profile summarizing the core service provider role and key protocol features for a network device.

This function queries the device using gNMI and analyzes its configuration to determine:

  • If MPLS is enabled (is_mpls_enabled)

  • If ISIS is enabled (is_isis_enabled)

  • If BGP L3VPN is enabled (is_bgp_l3vpn_enabled)

  • If the device is acting as a BGP Route Reflector (is_route_reflector)

  • If any non-default VPN/VRF has BGP IPv4 Unicast enabled (has_vpn_ipv4_unicast_bgp)

  • The overall device role (role): PE, P, RR, CE, or IGP-only

The resulting profile is essential for automation, troubleshooting, and intent-based operations in service provider networks. It allows higher-level systems (including LLMs) to:

  • Dynamically adjust what data to query (e.g., only look for VPNs on PE routers, ignore VPNs on P routers, avoid interface queries in VPNs on RRs, etc.)

  • Make topology-aware decisions and recommendations

  • Filter or target operational commands based on device function

  • Provide context-aware diagnostics and explanations

Example output for a PE device: { "is_mpls_enabled": true, "is_isis_enabled": true, "is_bgp_l3vpn_enabled": true, "is_route_reflector": false, "has_vpn_ipv4_unicast_bgp": true, "role": "PE" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_nameYesName of the device in inventory

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nosYesSupported Network Operating Systems
dataNo
statusYesEnumeration for network operation status values. Provides type safety and prevents typos when setting or checking operation status in NetworkOperationResult objects.
metadataNo
ip_addressYes
device_nameYes
error_responseNo
operation_typeYes
feature_not_found_responseNo
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description mentions it queries via gNMI and analyzes configuration, implying a read operation, but does not disclose potential performance impact, required permissions, or error cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is somewhat lengthy but well-structured with clear sections: function summary, what it determines, usage scenarios, and example output. Could be trimmed slightly but is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, detailed description of output fields, and example output, the description is fairly complete. Lacks explicit mention of return format (JSON already implied) but covers key aspects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'device_name' is fully covered by schema description. The description adds no additional semantics beyond acknowledging the device is in inventory, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states retrieving a comprehensive device profile with specific fields (MPLS, ISIS, BGP L3VPN, etc.) and distinguishes from sibling tools like get_routing_info or get_interface_info by focusing on role detection and protocol features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for usage: querying via gNMI to build a profile for automation, troubleshooting, and intent-based operations. Does not explicitly state when not to use, but the purpose is well-defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jillesca/gNMIBuddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server