Skip to main content
Glama
Self-hosted-MCP

NextDNS-Agent-MCP

by Self-hosted-MCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

chart

Read-only

Visualize a NextDNS profile's analytics as a PNG with line trends over time or top-row bar rankings. Use it to compare trends or rankings; it changes nothing.

Instructions

Draw a profile's analytics as a PNG picture: lines over time (up to 6) or bars of the top rows (up to 20), for the same reports as analytics. Use it when the user wants to see a trend or a ranking; use analytics for exact numbers and more rows. Changes nothing. Returns a short text with the totals plus the image, or only a note when there were no queries in that time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoBars only: how many rows, up to 20.
deviceNoOnly this device: a device ID from the devices report, or __UNIDENTIFIED__.
reportNoWhich report: status, domains, reasons, ips, devices, protocols, queryTypes, ipVersions, dnssec, encryption or destinations.status
statusNodomains report only: just blocked, allowed or default queries.
profileNoThe profile's ID or name. Leave empty for the only profile, or the default one.
to_dateNoWhere to stop, not included: an ISO date, Unix time or relative like -1h. Empty means now.
intervalNoWith over_time: the step between points, like 1h or 1d.
timezoneNoWith over_time: the time zone for the steps, like Europe/Lisbon.
from_dateNoWhere to start, included: an ISO date, Unix time or relative like -6h, -7d or -1M.-7d
over_timeNotrue: lines over time (up to 6). false: bars of the top rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / device / description
      Added value: +"Only this device: a device ID from the devices report, or __UNIDENTIFIED__."
    • addedInput schema / properties / from_date / description
      Added value: +"Where to start, included: an ISO date, Unix time or relative like -6h, -7d or -1M."
    • addedInput schema / properties / interval / description
      Added value: +"With over_time: the step between points, like 1h or 1d."
    • addedInput schema / properties / limit / description
      Added value: +"Bars only: how many rows, up to 20."
    • addedInput schema / properties / over_time / description
      Added value: +"true: lines over time (up to 6). false: bars of the top rows."
    • addedInput schema / properties / profile / description
      Added value: +"The profile's ID or name. Leave empty for the only profile, or the default one."
    • addedInput schema / properties / report / description
      Added value: +"Which report: status, domains, reasons, ips, devices, protocols, queryTypes, ipVersions, dnssec, encryption or destinations."
    • addedInput schema / properties / status / description
      Added value: +"domains report only: just blocked, allowed or default queries."
    • addedInput schema / properties / timezone / description
      Added value: +"With over_time: the time zone for the steps, like Europe/Lisbon."
    • addedInput schema / properties / to_date / description
      Added value: +"Where to stop, not included: an ISO date, Unix time or relative like -1h. Empty means now."
  2. First observedv0.8.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Changes nothing' is largely redundant repetition of the structured hint. However, the description adds genuinely non-structured behavior: the return payload is a short text with totals plus an image, or only a note when there were no queries in that time, plus the 6-line/20-bar caps. Return-shape disclosure is real added value beyond the 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?

Three sentences, front-loaded with the core action, then the routing rule, then the behavioral note. Dense but every sentence carries content; only minor redundancy in restating the line/bar caps already in the schema.

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

Completeness4/5

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

For a 10-parameter, no-required-params tool with no output schema, the description covers purpose, routing, mutation safety, and the return format (text totals + image, or a note when empty). It omits explicit guidance on interval/timezone requirements beyond 'with over_time', but the schema supplies those details, so completeness is strong overall.

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 the schema already documents all 10 parameters thoroughly (limit up to 20, device IDs, report enum-like list, over_time semantics, date formats). The description restates the 6-line/20-bar limits and the shared-report constraint but adds no new parameter syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource (draw a profile's analytics as a PNG) and specifies the two visual modes (lines over time up to 6, bars of top rows up to 20). It explicitly distinguishes itself from the sibling 'analytics' by scope ('same reports as analytics'), so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('when the user wants to see a trend or a ranking') and a named alternative with the condition that selects it ('use analytics for exact numbers and more rows'). This is a textbook when/when-not/alternative routing statement.

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