Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

updateDowntimeSchedule

Update an OpManager downtime schedule to change its name, status, recurrence, or assigned devices. Modify start/end times and frequency to align with maintenance windows.

Instructions

updateDowntimeSchedule

Key parameters:

  • operation: Edit will be sent by default (Edit).

  • MS_INSTANCEID: Downtime scheduler ID.

  • scheduleId: Downtime scheduler ID.

  • scheduleName: Downtime scheduler name.

  • status: Status will be set as Enabled by default.

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
enddayNoEnd day (month date, 32 for the last day of the month) for Monthly date-wise frequency.
statusNoStatus will be set as Enabled by default.
to_hrsNoEnd hour (00 to 23) for Monthly day-wise frequency.
to_minsNoEnd minute (00 to 59) for Monthly day-wise frequency.
to_timeNoEnd time (hh:mm) for Weekly downtime frequency.
weekdayNoDay of the week (Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday) for Monthly day-wise frequency.
from_hrsNoStart hour (00 to 23) for Monthly day-wise frequency.
startdayNoStart day (month date, 32 for the last day of the month) for Monthly date-wise frequency.
from_minsNoStart minute (00 to 59) for Monthly day-wise frequency.
from_timeNoStart time (hh:mm) for Weekly downtime frequency.
operationNoEdit will be sent by default (Edit).
once_endatNoEnd time (yyyy-mm-dd hh:mm).
recurrenceNoDowntime frequency (OnceOnly | Daily | Weekly | Monthly).
scheduleIdNoDowntime scheduler ID.
selectedBVNoSelected Business View.
monthlyTypeNoMonthly downtime type (monthlyDate | monthlyDay).
selectedURLNoSelected URLs.
weekOfMonthNoWeek of the month (1-5 or last week) for Monthly day-wise frequency.
once_startatNoStart time (yyyy-mm-dd hh:mm).
scheduleDescNoDowntime scheduler description.
scheduleNameNoDowntime scheduler name.
MS_INSTANCEIDNoDowntime scheduler ID.
selectedCategNoSelected category.
selectedDevicesNoSelected devices.
daily_effectfromNoEffect from date (yyyy-mm-dd) for Daily downtime frequency.
selectDevicesMethodNoFilter by option (Category | BV | Device | URL | GROUP).
selectedLogicalGroupNoSelected logical group.
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only mentions default values for operation and status, but does not disclose effects of updates (e.g., whether it overwrites existing settings), required permissions, or potential side effects.

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 very short but lacks structure. It starts with the tool name again and then lists a few parameters without any explanatory prose. It is underspecified rather than concise.

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

Completeness1/5

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

Given 29 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain parameter relationships, required inputs beyond host and apiKey, or what happens on success/failure.

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 tool description highlights only 5 of 29 parameters, repeating defaults already in schema descriptions. It adds minimal meaning beyond 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 description does not explicitly state that the tool updates a downtime schedule. It lists parameters like 'operation: Edit' which implies update, but the purpose is not clearly articulated. The name itself is indicative, but the description could be more explicit.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives like getDowntimeSchedule or listDownTimeSchedules. No context about use cases or exclusions is provided.

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