Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

listInterfaces

Retrieve a list of network interfaces from OpManager with filtering, sorting, and pagination options.

Instructions

listInterfaces

Category: Manage and query network devices

Key parameters:

  • isFluidic: Set value as 'true' by default (for internal purpose)

  • rows: To fetch interface list in batches. This should be combinedl

  • page: To fetch interface list in batches. This should be combinedl

  • sortByColumn: Sorting interfaces list with columns [Example: inSpeed, disp

  • sortByType: Defining ascending or descending sort of interfaces list [Ex

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
pageNoTo fetch interface list in batches. This should be combinedly used with 'rows' parameter [Example: page=1, rows=200, page=2, rows=200]
rowsNoTo fetch interface list in batches. This should be combinedly used with 'page' parameter [Example: page=1, rows=200, page=2, rows=200]
typeNoFilter interface with interface type. [Example: Ethernet,Software Loopback, etc]
apiKeyYesOpManager API key for authentication
severityNoFilter interfaces with severity. [Example: 1 (Critical), 2 (Trouble), 3 (Attention), 4 (service down), 5 (Clear), 7 (Unmanaged)]
intfPropsNoTo fetch additional interface properties such as ifName (Interface ifName), moid (internal managed object identifier used for interface/device), physAddress
isFluidicNoSet value as 'true' by default (for internal purpose)
sortByTypeNoDefining ascending or descending sort of interfaces list [Example, sortByType=asc Or sortByType=desc]
sortByColumnNoSorting interfaces list with columns [Example: inSpeed, displayName, ipaddress, outSpeed, statusNum, severity - 1 (Critical), 2 (Trouble), 3 (Attention), 4 (service down), 5 (Clear), 7 (Unmanaged)]
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions authentication (apiKey), pagination (rows/page), sorting, and filtering, but the description is incomplete and does not state that this is a read-only operation or describe side effects. The 'isFluidic' parameter is noted as internal but not fully explained.

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

Conciseness2/5

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

The description is poorly structured: it begins with the tool name, then 'Category:', then a fragmented list of key parameters that cuts off mid-word. It is not concise and lacks proper sentence structure.

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

Completeness2/5

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

With 10 parameters, 2 required, no output schema, and many sibling tools, the description should explain what data is returned and the scope. It does not provide sufficient context for an agent to use the tool effectively without further inference.

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?

The input schema has 100% description coverage, so the schema itself provides adequate semantic meaning. The description adds some parameter context but is truncated and redundant (e.g., rows and page descriptions are nearly identical). Baseline is 3, and the description does not significantly enhance understanding.

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

Purpose3/5

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

The tool name 'listInterfaces' and category 'Manage and query network devices' imply listing interfaces, but the description is truncated and lacks an explicit statement of what the tool does. It does not distinguish from siblings like 'getInterfaces' or 'getInterfaceSummary'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternative tools (e.g., getInterfaces, listDevices). There is no mention of prerequisites or context for use.

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/sachdev27/opmanager-mcp-server'

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