Skip to main content
Glama
Sign In
safe-omada-mcp

safe-omada-mcp

by gaspareduard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getQosPolicy

Get the gateway QoS policy (tag outbound traffic settings) for a site, including DSCP marking rules for outbound traffic.

Instructions

Get the gateway QoS policy (tag outbound traffic settings) for a site, including DSCP marking rules for outbound traffic.

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": "getQosPolicy"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdNoSite ID to target. If omitted, uses the default site from OMADA_SITE_ID config. Use listSites to discover available site IDs.
customHeadersNoOptional HTTP headers to include in the Omada API request (e.g. {"X-Custom-Header": "value"}). Rarely needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Get' implies a read-only operation and the description discloses the payload content (outbound DSCP tagging), but it says nothing about permissions, whether defaults are returned when no policy is configured, or what the response looks like.

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

Conciseness4/5

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

One front-loaded sentence with the verb and resource first; the parenthetical is slightly redundant with the trailing 'for outbound traffic' clause, but the description remains tight.

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

Completeness3/5

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

A simple two-parameter read tool, so the description is nearly sufficient, but with no output schema the agent gets no sense of the return shape, and the unresolved overlap with getQosMarkingRule/getDscpConfig/getQosPolicyRule leaves real ambiguity about which tool to invoke.

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 description coverage is 100%: siteId documents the OMADA_SITE_ID fallback and points to listSites, and customHeaders explains itself. The description adds no parameter meaning beyond 'for a site', so the schema does all the work and the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Get the gateway QoS policy') and names its content (tag outbound traffic settings, DSCP marking rules). However, it does nothing to distinguish itself from close siblings such as getQosMarkingRule, getDscpConfig, getQosPolicyRule, and getGatewayQosClassRules, which the description appears to overlap with.

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?

There is no guidance on when to call this versus the many adjacent QoS/DSCP/traffic-priority tools in the sibling list. The agent must infer selection from the name alone.

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