Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

getDeviceCompleteDetails

Retrieve all details for a device in OpManager by providing its name. Enables comprehensive device information access for network monitoring and troubleshooting.

Instructions

getDeviceCompleteDetails

Key parameters:

  • name*: Name of the device

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

Input Schema

NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
nameYesName of the device
apiKeyYesOpManager API key for authentication

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

The description gives no behavioral traits such as read-only, destructive, or return format. With no annotations, the description fails to disclose basic operational characteristics.

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 lacks substance. It is underspecified rather than concise, failing to provide essential information in a structured manner.

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 the tool's three required parameters, no output schema, and many sibling tools, the description is completely inadequate. It does not cover return values, prerequisites, or context for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description merely restates the 'name' parameter's schema description without adding meaning. It does not explain how the parameter is used or any constraints.

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

Purpose1/5

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

The description merely repeats the tool's name and parameter name without stating what the tool does. It lacks a verb and resource, providing no distinct purpose beyond the name itself.

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?

No guidance on when to use this tool versus similar siblings like getDeviceSummary or getDeviceInfo. No context or exclusions are provided.

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