Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

getLogicalGroupInfo

Retrieve availability metrics and snapshot details for a logical group in OpManager by specifying the group name, time period, and snapshot type.

Instructions

getLogicalGroupInfo

Key parameters:

  • groupName*: Name of the group with MOID appended in the suffix. such as

  • period: Time for which the availability data is to be fetched.[Examp

  • snapType: Group Snapshot type. [Example: LogicalGroup|LogicalIntfGroup

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
periodNoTime for which the availability data is to be fetched.[Example: twelvehours(16),Today(6),twfourhours(3),Yesterday(7),thisweek(8),Last_7_Days(4),lastweek(9),thismonth(10),Last_30_Days(5),Last_Month(11),custom(23)]
snapTypeNoGroup Snapshot type. [Example: LogicalGroup|LogicalIntfGroup|LogicalDeviceGroup]
groupNameYesName of the group with MOID appended in the suffix. such as -

Tool Definition Quality

D1.5/5.0
Behavior1/5

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

No annotations exist and the description does not disclose behavioral traits such as authentication, side effects, or response handling. It is completely opaque.

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?

Very short but incomplete sentences (e.g., 'such as -', '[Examp'). Not properly structured or front-loaded; appears truncated.

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?

Multiple parameters, no output schema, and no description of return values or behavior. The description is far from complete for a tool of this complexity.

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 adds minimal meaningful context beyond the parameter names, and includes incomplete examples. Baseline 3 but degraded due to poor quality and incomplete hints.

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 lacks a clear verb and resource; it merely lists parameters without stating what the tool returns or does. The name suggests 'get info' but the text is incomplete and doesn't specify the purpose.

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 alternatives. With many sibling tools, no context for selection is provided.

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