Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

getReportsData

Retrieves OpManager report data by report ID, time period, and optional filters such as excluded days, business hours, and custom time windows for analysis.

Instructions

getReportsData

Key parameters:

  • reportID: Unique ID for individual reports.

  • viewAs: Format to view the resultant report data.

  • time: The time period to fetch the report data.

  • isExcludeDays: Boolean value to exclude days or not.

  • excludedDays: The day to be excluded in report data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoTo show the top of the reports data.
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
timeNoThe time period to fetch the report data.
bviewNoThe business view to view the report data.
apiKeyYesOpManager API key for authentication
viewAsNoFormat to view the resultant report data.
endHourNoEnd hour of custom time period.
endTimeNoEnd time of custom time period.
categoryNoThe category to view the report data.
reportIDNoUnique ID for individual reports.
showTypeNoTo show the top or bottom contents of report data.
startHourNoStart hour of custom time period.
startTimeNoStart time of custom time period.
toEmailidNoTo mail id for report to be sent.
customerIdNoProbe Id to be filtered.
timeWindowNoThe time window to fetch the report data.
fromEmailidNoFrom mail id for report to be sent.
customerNameNoProbe name to be filtered.
emailSubjectNoMail Subject
excludedDaysNoThe day to be excluded in report data.
logicalGroupNoThe logical group to view the report data.
isExcludeDaysNoBoolean value to exclude days or not.
businessRuleIDNoID of the business rule created previously.
isBusinessHourNoBoolean value to show business hour data or not.
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects, idempotency, authentication requirements, or other behavioral traits. It only lists parameters.

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 a simple bullet list, which is structured but not concise. It could be more efficient by including a clear purpose sentence and grouping related parameters.

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?

With 24 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return format, pagination, or any constraints beyond parameter lists.

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%, so the schema already describes all parameters. The description essentially repeats parameter names and brief descriptions without adding new information beyond what is already in the schema.

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 does not state what the tool does beyond its name. It merely lists key parameters without specifying the verb-resource relationship. The sibling tool 'getReportData' could be similar, but no differentiation is provided.

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 'getReportData' or 'getReportsList'. The description lacks context for appropriate usage scenarios.

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