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

safe-omada-mcp

by gaspareduard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getUpgradeOverviewCritical

Retrieve the count of critical firmware upgrades for managed devices to prioritize security patches and prevent vulnerabilities.

Instructions

Get the number of critical firmware upgrades available across managed devices.

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

Input Schema

NameRequiredDescriptionDefault
customHeadersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic function, without any mention of side effects, permissions, rate limits, or return behavior. The agent has no information about the safety or side effects of this call.

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 a single sentence of 9 words, concise and front-loaded. However, it is so brief that it sacrifices necessary detail; still, it avoids unnecessary words.

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?

The tool has one undocumented parameter and no output schema. The description does not hint at the return format (e.g., whether it returns a number, object, or list). Given the complexity of the sibling tools and the lack of schema coverage, the description is insufficient for complete understanding.

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

Parameters1/5

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

The input schema has one parameter (customHeaders) with no description in the schema (0% coverage) and the tool description does not explain its purpose, format, or usage. The description adds zero value beyond the schema for parameter understanding.

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?

The description clearly states the verb 'Get', the resource 'the number of critical firmware upgrades', and the scope 'across managed devices'. It is specific and distinguishes from sibling tools like getFirmwareUpgradePlan which provides more detailed plans.

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

Usage Guidelines3/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. The description implies it is for obtaining a count of critical upgrades, but does not specify when to prefer it over getFirmwareUpgradePlan or getUpgradeOverviewTryBeta.

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