Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

listAlarms

Retrieve alarms from OpManager by device, severity, category, alert type, or time range to monitor network issues.

Instructions

listAlarms

Category: Manage and query alarms/alerts in OpManager

Key parameters:

  • deviceName: Device Name of the alarm. The device name can be taken from

  • severity: Severity of the alarm. The severity could range anywhere fro

  • category: Device category of the alarm

  • alertType: alertType of the alarm. The alert type can be any of the fol

  • fromTime: Start time for the custom time period range. It could be of

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
apiKeyYesOpManager API key for authentication
toTimeNoEnd time for the custom time period range. It could be of the format yyyy-mm-dd or yyyy-mm-dd hh:mm:ss. If no time is specified (i.e, yyyy-mm-dd format), the default time will be set to 12 A.M(start of the day).
categoryNoDevice category of the alarm
fromTimeNoStart time for the custom time period range. It could be of the format yyyy-mm-dd or yyyy-mm-dd hh:mm:ss. If no time is specified (i.e, yyyy-mm-dd format), the default time will be set to 12 A.M(start of the day).
severityNoSeverity of the alarm. The severity could range anywhere from 1 to 5. 1 = Critical, 2 = Trouble, 3 = Attention, 4 = Service Down, 5 = Clear .
alertTypeNoalertType of the alarm. The alert type can be any of the following: ActiveAlarms, EventLogAlarms, SyslogAlarms, TrapAlarms, NCMAlarms, NFAAlarms, WebAlarms, FWAAlarms, StorageAlarms .
probeNameNoThe name of the Probe. The probe name could be obtained by executing the listProbes API , where the parameter name in the response refers to the probeName. [Applicable only for Central Server]
deviceNameNoDevice Name of the alarm. The device name can be taken from the URL of the device snapshot page.

Tool Definition Quality

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only says 'listAlarms' and 'Manage/query', with no mention of side effects, read-only nature, pagination, or order. The truncated sentences provide no additional insight.

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 repeats the tool name, then a vague category, then a list of parameter names with cut-off descriptions. This wastes space and does not efficiently convey information.

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 9 parameters and no output schema, the description should explain the return format, filtering behavior, and pagination. It fails to do so, and is truncated, leaving significant gaps in understanding.

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 parameters are already well-documented. The tool description attempts to list them but is truncated and adds no new meaning. Baseline 3 applies; no extra value but no harm.

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 description states 'listAlarms' and 'Manage and query alarms/alerts', indicating a listing operation. However, it is vague ('Manage' could imply modification) and does not differentiate from sibling tools like 'clearAlarm' or 'acknowledgeAlarm'. The truncated parameter list adds confusion.

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 versus alternatives. The sibling list includes many alarm-related tools, but the description provides no contextual hints or exclusions.

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