Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

setDeviceInfo

Specify a network device and update its hardware details including Model, SoftwareVersion, OperatingSystem, RAM, HDD, and Manufacturer by providing metric-value pairs.

Instructions

setDeviceInfo

Category: Manage and query network devices

Key parameters:

  • deviceName/ipAddress/dnsName*: Either one of these three parameters can be used to update t

  • values*: The JSON array containing metricName and metricValue for Har

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
valuesYesThe JSON array containing metricName and metricValue for Hardware details update: (a) metricName - The Hardware metric(s) that need to be changed. These metrics include Model, SoftwareVersion, OperatingSystem, RAM, HDD, and Manufacturer. [Note: These metrics are case-sensitive and must be used as it is] (b) metricValue - The value corresponding to the respective metricName to be changed.
deviceName/ipAddress/dnsNameYesEither one of these three parameters can be used to update the device details. These parameters are the managed Entity name as seen in the URL of the device snapshot page (OR 'deviceName' property value in the listDevices API response), or the IP address of the device, or the DNS name of the device.
Behavior2/5

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

No annotations provided; description does not specify mutability, overwrite behavior, required device state, or side effects. Minimal behavioral disclosure.

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

Conciseness3/5

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

The description is short (3 lines) but one line is truncated, making it feel incomplete. It front-loads category but wastes space repeating parameter names.

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?

No output schema; description fails to explain return values, success/failure indicators, or rate limits. Incomplete for a mutation tool that modifies device state.

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 baseline is 3. Description highlights key parameters but adds no additional meaning beyond the schema description; it is largely redundant.

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 is truncated but, combined with the input schema, indicates the tool updates hardware details. However, it lacks a clear verb+resource statement; the category line is too generic.

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 on when to use this tool versus alternatives like getDeviceInfo or other mutation tools. No when-not-to-use or prerequisite conditions.

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