Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

getDownDevices

Retrieve a list of currently down devices from OpManager to quickly identify network issues and take corrective action.

Instructions

getDownDevices

Category: Discover new devices on the network

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>"
    },
    "name": "getDownDevices"
  }
}

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

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?

No annotations exist, and the brief description fails to disclose behavioral traits such as whether the tool is read-only, what side effects occur, or how 'new' or 'down' devices are defined. The description is inadequate.

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 short but at the cost of necessary detail. It is under-specified, lacking essential context that would justify its brevity.

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?

For a network monitoring tool with no output schema and no annotations, the description is far too sparse. It does not explain the return format, the meaning of 'down' vs. 'new,' or how results differ from sibling tools like getDeviceInfo.

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% with clear descriptions for both parameters. The description adds no further meaning beyond the schema, so a baseline score of 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 states 'Discover new devices on the network,' but the tool name 'getDownDevices' suggests retrieving down devices, not new ones. This contradiction creates ambiguity about the actual purpose.

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 like listDevices. Given the name vs. description discrepancy, it's unclear if this is for down devices or new device discovery.

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