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

safe-omada-mcp

by gaspareduard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getGridAllowList

Get the IPS allow list (paginated). Returns entries that are explicitly allowed to bypass IPS inspection. Supports optional keyword search.

Instructions

Get the IPS allow list (paginated). Returns entries that are explicitly allowed to bypass IPS inspection. Supports optional keyword search.

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

Input Schema

NameRequiredDescriptionDefault
pageNoStart page number. Start from 1.
siteIdNoSite ID to target. If omitted, uses the default site from OMADA_SITE_ID config. Use listSites to discover available site IDs.
pageSizeNoNumber of entries per page. Range: 1-1000.
searchKeyNoOptional search keyword to filter IPS allow-list entries.
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?

With no annotations, the description carries the full burden. It discloses that results are paginated and what the list represents, and 'Get' implies a read. It does not state permission or authentication requirements, rate limits, or that this is a read-only operation without side effects, leaving meaningful behavioral gaps.

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?

Three short sentences, front-loaded with the resource and pagination, then the meaning of the entries, then the search option. No filler, though the parenthetical '(paginated)' is slightly redundant with the dedicated parameter descriptions.

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?

No output schema exists, so the description should characterize the returned entries more concretely (fields such as name, MAC/IP, enable state); it only says they are allowed to bypass IPS. Given five parameters with full schema coverage and no annotations, the definition is adequate but leaves the agent guessing about result shape and sibling choice.

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%, so page, pageSize, siteId, searchKey and customHeaders are all already documented with defaults, ranges and the listSites hint. The description's mention of pagination and keyword search adds no semantics beyond the schema, so the baseline 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 IPS allow list) and clarifies what the entries mean: explicitly allowed to bypass IPS inspection. However, it never distinguishes itself from the obvious sibling getGridBlockList, which is the main ambiguity an agent faces when choosing between the two.

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 when-to-use or when-not-to-use guidance, and no mention of the counterpart getGridBlockList or any other alternative. The only usage hint is implicit: 'supports optional keyword search' suggests passing searchKey to narrow results.

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