Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

associateServiceMonitor

Associate one or more services to a device in ManageEngine OpManager. Specify device and service names to link monitoring services directly.

Instructions

associateServiceMonitor

Key parameters:

  • deviceName*: Name of the device for which the service to be associated. G

  • serviceName*: Name of the service(s) (multiple values separated by commas)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "apiKey": "<apiKey>",
      "deviceName": "<deviceName>",
      "serviceName": "<serviceName>"
    },
    "name": "associateServiceMonitor"
  }
}

Input 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
deviceNameYesName of the device for which the service to be associated. Give the names by comma separated for bulk association
serviceNameYesName of the service(s) (multiple values separated by commas).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

The description provides no behavioral traits such as whether the operation is idempotent, requires specific permissions, or what happens on failure. Since annotations are absent, the description bears full responsibility, which it fails to meet.

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 extremely brief, consisting only of a heading and a parameter list with incomplete sentences. It lacks proper structure and fails to convey sufficient information.

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?

With no output schema, annotations, and 4 required parameters, the description does not cover return values, error handling, prerequisites, or potential side effects, making it highly inadequate for an agent to use correctly.

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 schema already documents all parameters. The description adds minimal value by restating parameter names and mentioning 'bulk association' for deviceName and serviceName, which is also noted in the schema descriptions.

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 consists of the tool name followed by a list of parameters, but does not explicitly state that this tool associates a service monitor to a device. The purpose is inferred from the name and parameter names, but not clearly articulated.

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 siblings like 'addServiceMonitor' or 'associateProcessMonitor'. The description mentions bulk association via comma-separated values, but lacks comparative context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools