Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

getBusinessDetailsView

Retrieve comprehensive details of a business view in OpManager by providing its name. Use this to access view configuration and associated data.

Instructions

getBusinessDetailsView

Key parameters:

  • bvName*: Name of the Business View (as shown in the URL of Business V

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "apiKey": "<apiKey>",
      "bvName": "<bvName>"
    },
    "name": "getBusinessDetailsView"
  }
}

Input 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
bvNameYesName of the Business View (as shown in the URL of Business View page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

The description does not disclose any behavioral traits such as read-only nature, authentication requirements, or rate limits. Since no annotations are provided, the description fails to compensate.

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 very short but incomplete and cut off. It front-loads the tool name unnecessarily and fails to deliver a complete thought, making it poorly structured for usefulness.

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 the tool has 3 parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain return values, prerequisites, or use cases, leaving the agent without essential information.

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?

All three parameters have descriptions in the schema, achieving 100% coverage. The description adds minimal extra meaning beyond repeating the bvName parameter, but the schema already provides sufficient semantics.

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 incomplete and merely repeats the tool name with a partial parameter list. It does not clearly state that the tool retrieves details of a business view, leaving the purpose vague.

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 usage guidance is provided. There is no differentiation from sibling tools like getBusinessView, and no conditions for when to use this tool are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools