Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

getIntfAtAGlanceReportDetails

Retrieve interface at-a-glance report details, including performance data, for a specified interface and time period from OpManager.

Instructions

getIntfAtAGlanceReportDetails

Key parameters:

  • InterfaceName*: Name of the interface - Managed Entity name as seen in the U

  • period*: Period for which the interface data is required. [Example: t

  • startDate: From Date. This parameter is applicable only if 'custom' tim

  • endDate: To Date. This parameter is applicable only if 'custom' time

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
periodYesPeriod for which the interface data is required. [Example: twelvehours,Today,twfourhours,Yesterday,thisweek,Last_7_Days,lastweek,thismonth,Last_30_Days,Last_Month,custom]
endDateNoTo Date. This parameter is applicable only if 'custom' time is opted in period param value
startDateNoFrom Date. This parameter is applicable only if 'custom' time is opted in period param value
InterfaceNameYesName of the interface - Managed Entity name as seen in the URL of interface snapshot page OR 'interfaceName' property value in the listInterfaces API response.

Tool Definition Quality

D1.5/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, side effects, or output characteristics. It solely lists parameters without transparency.

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 short but poorly structured, with broken sentences and missing information. It is concise in length but fails to convey a complete message.

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 no output schema and many similar sibling tools, the description is extremely incomplete. It does not clarify what the report contains, how it differs from other interface reports, or any prerequisite conditions.

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?

Although schema coverage is 100%, the description provides incomplete and truncated parameter explanations (e.g., 'as seen in the U', 'Example: t'), which are less informative than the schema. It adds confusion rather than value.

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 restates the tool name and lists key parameters but does not clearly explain what the tool does. It is incomplete and vague, failing to specify that it retrieves an 'at a glance' report for an interface.

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 is provided on when to use this tool versus similar sibling tools like getInterfaces or getInterfaceSummary. The description lacks any context for selection.

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