Skip to main content
Glama
Sign In
omada-mcp

omada-mcp

by dfla-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get site settings

get_site_settings
Read-only

Aggregates site-level wireless settings including roaming, band steering, and mesh by reading multiple Open API endpoints in parallel.

Instructions

Aggregate site-level wireless settings: roaming (fast roaming, AI roaming, force-disassociation, non-stick, 802.11k report), band steering and mesh. Reads three Open API endpoints in parallel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_site_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdNoOverride the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds that it reads three Open API endpoints in parallel and lists the specific settings included, enhancing behavioral understanding.

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?

Two concise sentences: one listing settings, one adding technical detail. No wasted words.

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?

Given no output schema, the description covers the purpose and key settings, but could mention output format or error handling for full completeness.

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 one parameter (siteId) described as 'Override the default site.' The description does not add further parameter meaning beyond the schema.

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 clearly states it aggregates site-level wireless settings like roaming, band steering, and mesh, distinguishing it from per-AP or per-SSID siblings such as get_ap_radios or get_ssid.

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

Usage Guidelines4/5

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

The description implies use for site-level aggregate settings, but does not explicitly state when not to use it or name alternatives. It provides clear context for usage.

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