tplink-omada-mcp

getGridAutoCheckUpgrade

Retrieves the auto-check upgrade schedule for devices, listing planned firmware upgrade checks to identify devices due for automatic updates and audit upgrade plans.

Instructions

Get the auto-check upgrade plan list showing scheduled firmware upgrade checks across devices. Useful for auditing upgrade schedules and identifying devices due for automatic firmware updates.

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

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.15.0Sep 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

No annotations provided, so the description carries full burden. It describes the tool as retrieving a list, which implies a read operation, but does not disclose behavioral details such as pagination behavior (despite params for page/pageSize), response structure, or whether it is read-only. Basic transparency is present.

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?

The description is two sentences, concise and front-loaded with the main purpose. Every sentence adds value, though it could be slightly more efficient by combining the second sentence with the first.

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

Completeness2/5

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

Given no output schema and no annotations, the description is incomplete. It does not specify what fields the response contains, how pagination is handled, or any potential cost (e.g., rate limits). For a list tool, more detail is needed for complete contextual understanding.

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% (page and pageSize described in schema). The description does not mention any parameters or provide additional meaning beyond what the schema already offers. 'customHeaders' is undocumented in both schema and description, leaving a gap.

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 it retrieves the auto-check upgrade plan list showing scheduled firmware upgrade checks. It uses a specific verb ('Get') and resource ('auto-check upgrade plan list'). It is distinct from sibling tools like getFirmwareUpgradePlan, though not explicitly differentiated.

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?

The description implies usage for auditing schedules but provides no explicit guidance on when to use this tool versus alternatives (e.g., getFirmwareUpgradePlan, getUpgradeLogs). No when-not or exclusion criteria are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server