Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

getWirelessAPList

Retrieves the list of wireless access points managed by a specific WLC device in OpManager. Helps monitor and troubleshoot wireless network infrastructure.

Instructions

getWirelessAPList

Key parameters:

  • deviceName*: Name of the WLC device (Managed Entity name seen in the URL

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>",
      "deviceName": "<deviceName>"
    },
    "name": "getWirelessAPList"
  }
}

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
deviceNameYesName of the WLC device (Managed Entity name seen in the URL of device snapshot page OR 'deviceName' property value in the listDevices API response)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior1/5

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

With no annotations provided, the description fails to disclose any behavioral traits, such as read-only nature, side effects, or authentication requirements. The description is empty of such context.

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 extremely short but appears truncated (ends mid-sentence). It lacks structure and does not effectively communicate essential information, making it under-specified rather than concise.

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 lack of output schema and behavioral annotations, the description fails to provide sufficient context about the tool's return value, usage constraints, or data interpretation. It is incomplete for effective agent usage.

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 coverage is 100%, so the schema already defines all parameters. The description merely highlights 'deviceName' but adds no new semantic value beyond what the schema provides. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely repeats the tool name 'getWirelessAPList' without stating what it does, such as 'Retrieves a list of wireless access points'. It is a tautology, providing no functional explanation.

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 is given on when to use this tool versus siblings like getSSIDClientList or getWirelessNetworkDetails. There is no context on prerequisites or preferred scenarios.

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