safe-omada-mcp

listUpgradeFirmwares

Retrieve a paginated list of uploaded firmware files for manual device upgrades. Specify page and page size to control results.

Instructions

List uploaded firmware files available for manual upgrade.

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

Input Schema

Name	Required	Description
`page`	No	Start page number. Start from 1.
`pageSize`	No	Number of entries per page. Range: 1-1000.
`customHeaders`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.17.0Jun 19, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavior. It only says 'list', implying a safe read, but omits details about pagination limits, authentication needs, or any side effects.

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

Conciseness3/5

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

The description is concise (one sentence) but minimally informative. It could be slightly expanded to include key details without being verbose.

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?

For a simple list tool with no output schema, the description is basic. It lacks context about return format, filtering, or ordering. Still, it covers the core purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, but the description adds no extra meaning to the parameters (page, pageSize, customHeaders). The customHeaders object lacks explanation.

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?

The description clearly states the verb 'list' and the resource 'uploaded firmware files', indicating a read operation. It implicitly distinguishes from siblings like getFirmwareInfo or getFirmwareUpgradePlan by focusing on the list of available files.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, filters, 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