Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

setManaged

Enable or disable monitoring for network devices, interfaces, or URLs by setting the manage parameter to true or false.

Instructions

setManaged

Category: Manage and query network devices

Key parameters:

  • manage*: Enables monitoring of devices or interfaces if manage=true,

  • name*: Name of the device or interface. (Managed Entity name as see

  • type: Set type as 'INTERFACE' if the managed entity is an interfac

  • isInterface: This parameter will take effect only when the value 'INTERFA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
nameYesName of the device or interface. (Managed Entity name as seen in the URL of device/interface snapshot page OR 'deviceName' property value in the listDevices API response)
typeNoSet type as 'INTERFACE' if the managed entity is an interface. Set type as 'URL' if the managed entity is an Url monitor.
apiKeyYesOpManager API key for authentication
manageYesEnables monitoring of devices or interfaces if manage=true, disables monitoring if manage=false
isInterfaceNoThis parameter will take effect only when the value 'INTERFACE' is supplied to type param. Set the value for this param as 'true' if the managed entity is an interface. By default, the entity will be assumed as device, hence it is not required to pass this parameter for managing device.
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, permissions required, or reversibility. The truncated text only hints at enabling/disabling monitoring, but details like rate limits, destructive potential, or authorization needs are absent.

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

Conciseness1/5

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

The description is clearly incomplete and cut off mid-sentence, making it unusable as a coherent explanation. It lacks proper structure and fails to be concise or informative.

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?

For a tool with 6 parameters and no output schema or annotations, the description should provide a complete overview, but it is truncated. Important context like return values, error handling, and usage examples are missing, leaving the agent poorly informed.

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 coverage is 100%, so the input schema already provides detailed descriptions for all 6 parameters. The description's parameter list is truncated and adds minimal new information beyond what the schema offers. Baseline 3 is appropriate.

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

Purpose2/5

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

The description is truncated and does not explicitly state the tool's purpose. It starts with a category label and lists key parameters but fails to provide a clear verb+resource statement. The name 'setManaged' suggests managing monitoring state, but the description is incomplete, leaving the purpose ambiguous.

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 alternatives. There is no mention of prerequisites, when-not scenarios, or sibling tools like 'setDeviceInfo' or 'listDevices'. The description is too brief to offer any usage context.

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