unifi-mcp-server

query-isp-metrics

Read-only

Monitor ISP performance by querying latency, uptime, and speed metrics with filters for hosts, sites, and durations.

Instructions

Query ISP metrics with filters. May be unavailable depending on account

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": "query-isp-metrics"
  }
}

Input Schema

Name	Required	Description
`hostIds`	No	Filter by host IDs
`siteIds`	No	Filter by site IDs
`duration`	No	Time duration (e.g., '1h', '24h', '7d')
`metricType`	No	Type of ISP metric to query

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.4May 22, 2026
Removedv1.12.3May 15, 2026
First observedv1.11.1May 6, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds a useful behavioral caveat that the tool may be unavailable depending on account, complementing the open-world hint. No contradiction with annotations.

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?

Description is very short (two sentences) but front-loads the purpose. Could add more context without being verbose, but current structure is efficient.

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?

While annotations cover safety and variability, the description lacks information on output format or result structure. Given no output schema and enum values without explanations, more detail would help.

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 all parameters are already documented in the schema. Description only vaguely mentions 'filters', adding no new semantic information beyond schema. Baseline 3 is appropriate.

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?

Description clearly states verb (query) and resource (ISP metrics) with filters. However, it does not differentiate from sibling tool 'get-isp-metrics', which may have similar function. Slight ambiguity but not a tautology.

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 vs alternatives. The mention of potential unavailability is a behavioral note, not usage context. No exclusions or conditions for using this tool.

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