Skip to main content
Glama
Sign In
omada-mcp

omada-mcp

by dfla-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get SSID detail

get_ssid
Read-only

Retrieve full SSID configuration by providing SSID id. Automatically discovers the WLAN group if not specified.

Instructions

Full SSID configuration. If wlanId is omitted, the tool finds the owning WLAN group automatically via list_ssids.

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": {
      "ssidId": "<ssidId>"
    },
    "name": "get_ssid"
  }
}

Input Schema

NameRequiredDescriptionDefault
ssidIdYesSSID id (from list_ssids).
wlanIdNoWLAN-group id (auto-discovered if omitted).
siteIdNoOverride the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only and open-world behavior. The description adds contextual transparency by explaining the automatic WLAN group discovery via 'list_ssids', which is a significant behavioral trait beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the purpose ('Full SSID configuration') and then adds the key behavioral nuance about auto-discovery. Every word is informative with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core functionality and key behavioral trait (auto-discovery) adequately. Given the presence of annotations and 100% schema coverage, it provides sufficient context for an agent to decide when to invoke the tool. Minor gap in not describing the output format, but output schema is absent.

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% with clear parameter descriptions. The overall description adds minimal new meaning beyond the schema, only reinforcing the auto-discovery aspect for 'wlanId'. Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description states 'Full SSID configuration' clearly indicating the tool retrieves complete configuration details for a specific SSID. It also distinguishes itself by describing the automatic WLAN group discovery when 'wlanId' is omitted, which differentiates it from a basic get tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implicit usage guidance by explaining the auto-discovery behavior for the 'wlanId' parameter and hints that 'ssidId' comes from 'list_ssids'. However, it does not explicitly state when to use this tool over siblings or when not to use it.

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