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

safe-omada-mcp

by gaspareduard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getApplicationAcl

[DEPRECATED] Get application control rules for a site. This is an alias for getAppControlRules — use getAppControlRules instead.

Instructions

[DEPRECATED] Get application control rules for a site. This is an alias for getAppControlRules — use getAppControlRules instead.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based).
siteIdNoSite ID to target. If omitted, uses the default site from OMADA_SITE_ID config. Use listSites to discover available site IDs.
pageSizeNoNumber of results per page (1–1000).
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

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does contribute one high-value fact: the tool is deprecated and is an alias. However, it does not say whether results and parameters are identical to getAppControlRules, whether the alias may be removed, or whether pagination behaves the same, leaving real ambiguity for a read tool with nested header params.

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 sentences, zero waste, and the deprecation marker plus the redirect are front-loaded so the agent sees the actionable information first. Nothing repeats schema or title content.

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?

For a deprecated alias of a fully schema-documented read tool with no output schema, this is nearly sufficient: it flags deprecation and the replacement. The only missing piece is confirmation that inputs/outputs are identical to getAppControlRules, which would fully close the loop.

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% – page, pageSize, siteId (with listSites pointer) and customHeaders are all documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Get application control rules for a site') and immediately identifies itself as an alias of getAppControlRules, which is present in the sibling list. An agent can distinguish this tool's intent from the ~100 other getters without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent away from this tool ('use getAppControlRules instead') and names the exact alternative, which is the correct guidance for a deprecated alias. This is a when-not-to-use directive with a concrete sibling substitute.

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