fios-mcp

Overview Schema Source Related Servers Discussions Admin

get_dmz_settings

Read-only

Retrieve the router's DMZ host settings to identify which local device is exposed to the internet and verify the current firewall/DMZ configuration.

Instructions

DMZ host settings.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on what the settings block contains, whether values can be blank/unset, or how it pairs with set_dmz.

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?

It is short and waste-free, but that brevity reflects under-specification rather than disciplined editing. There is no front-loaded statement of action or purpose to anchor the sentence.

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?

An output schema exists, so return values need not be explained, and there are no parameters to document. Even so, a DMZ-read tool in a family containing set_dmz should say at minimum that it reads the current DMZ host configuration and that set_dmz mutates it; that context is entirely absent.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"DMZ host settings." is a noun phrase that essentially restates the tool name get_dmz_settings; it names no verb (read/retrieve) and gives no scope or sibling differentiation. An agent cannot tell from this text how it differs from set_dmz or get_firewall_settings.

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?

There is no when-to-use guidance, no mention of set_dmz as the write counterpart, and no prerequisite or exclusion stated. Read-only usage is only implied by the 'settings' noun, not declared.

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