Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

getReportData

Retrieve report data from OpManager for specified devices and monitors over a given time period, viewable in table or graph format.

Instructions

getReportData

Key parameters:

  • deviceList: Device list to fetch the report data.

  • monitorList: Monitor list to fetch the report data.

  • timePeriod: Time period to fetch the report data.

  • view: Viewing report in table/graph format.

  • tableView: To show the report data in instance/Monitor wise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
viewNoViewing report in table/graph format.
apiKeyYesOpManager API key for authentication
endDateNoEnd date of the report data.
endHourNoEnd hour of the report data.
startDateNoStart date of the report data.
startHourNoStart hour of the report data.
tableViewNoTo show the report data in instance/Monitor wise.
deviceListNoDevice list to fetch the report data.
timePeriodNoTime period to fetch the report data.
timeWindowNoThe time window to fetch the report data.
monitorListNoMonitor list to fetch the report data.
combinedTableNoBoolean value to show combined table results.
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as read-only vs destructive, authentication requirements, rate limits, or side effects. For a data-fetching tool, this is a critical omission.

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 very short, but it is not front-loaded with a clear purpose. It merely lists a subset of parameters without a narrative. While concise, it sacrifices clarity for 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?

Given 13 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain the tool's overall function, return value, or how parameters interact. User cannot effectively invoke this tool based on the description alone.

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 description coverage is 100%, so baseline is 3. The description lists some parameters but adds no extra meaning beyond what the schema already provides. It does not explain formats, valid values, or relationships between parameters.

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 is a tautology: 'getReportData' just restates the name. It does not specify what kind of report data, from which source, or how it differs from siblings like 'getReportsData' or 'getReportsList'. The verb is vague and the resource is underspecified.

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. Sibling tools exist (e.g., getReportsData, getReportsList) but the description gives no context for selection. No prerequisites or exclusions are mentioned.

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