Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

listDevices

Retrieve a filtered list of devices from OpManager by type, category, vendor, severity, or group to monitor network infrastructure.

Instructions

listDevices

Category: Manage and query network devices

Key parameters:

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

  • type: Fetches the list of devices that fall under the given Device

  • category: Fetches the list of devices that fall under the given device

  • app: Fetches the list of devices that have the given App in it an

  • bvName: Fetches the list of devices that are under the given Busines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoFetches the list of devices that have the given App in it and monitored in OpManager Plus [Example: MSSQL, Exchange, Domain Controller]
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
pageNoTo fetch devices in batches. This should be combinedly used with 'rows' parameter. [Example: page=1, rows=200, page=2, rows=200]
rowsNoTo fetch devices in batches. This should be combinedly used with 'page' parameter [Example: page=1, rows=200, page=2, rows=200]
typeNoFetches the list of devices that fall under the given Device Type. [Example: type=Cisco2081]
apiKeyYesOpManager API key for authentication
bvNameNoFetches the list of devices that are under the given Business View map name
vendorNoFetches the list of devices that have the given vendor name.
categoryNoFetches the list of devices that fall under the given device category [Example: Server, Switch, etc.]
protocolNoFilter devices by protocol [Example: all|SNMP|WMI|CLI|VIWebService|VIWMI|CLI|XenService|PrismAPI|NetAppAPI|SMI]
severityNoFilter devices by severity [Example: 1 (Critical), 2 (Trouble), 3 (Attention), 4 (service down), 5 (Clear), 7 (Unmanaged)]
groupNameNoFilter devices by Group name
isFluidicNoSet value as 'true' by default.(for internal purpose)
sortByTypeNoDefining sort type to be ascending or descending  [Example, sortByType=asc Or sortByType=desc]
customFieldsNoTo fetch custom field values for the devices, supply the required custom field names in the 'customFields' param in the API request. Example: /api/json/device/listDevices?apiKey=***************&customFields=Building,Comments,Floor
sortByColumnNoSorting device list by columns [Example: displayName, interfaceCount, ipaddress, type, etc.]
getInterfacesNoTo fetch devices with associated interfaces. Boolean value: TRUE/FALSE
selectedVTypesNoFilter devices by Virtual device type [Example: VMware-VM|VMware-Host|HyperV-VM|Xen-VM|VMware-vCenter|Xen-Host|HyperV-Host]
Behavior2/5

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

No annotations provided; description fails to disclose behavior such as pagination limits, default filters, authentication details, or the structure of the response. Only lists parameters without behavioral context.

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

Conciseness3/5

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

Description is somewhat structured but includes redundant header 'listDevices' and truncated lines in the parameter list. Could be more concise and better formatted.

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 18 parameters and no output schema or annotations, the description is incomplete. It lacks explanation of pagination, sorting, and response format, which are critical for effective use.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema, as it repeats some parameter names but not more than what is already in the schema.

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 'listDevices' clearly indicates listing devices, but the description is vague ('Manage and query network devices') and does not specify the exact action or differentiate from siblings like 'listAllDevicesSpecificURLs' or 'listInterfaces'.

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 on when to use this tool vs alternatives. The description lacks context for selection among the many device-related tools.

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