firewall-aiops

nat_one_to_one

Read-only

Reads normalized 1:1 NAT mappings between external and internal addresses, optionally for a specified firewall target.

Instructions

[READ] 1:1 NAT mappings (external ↔ internal), normalized.

Args: target: Firewall target name from config; omit for the default.

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

Input Schema

Name	Required	Description	Default
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Aug 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

readOnlyHint=true already establishes the safety profile, and the [READ] tag aligns with it. The description adds that output is normalized and the mapping is external↔internal, but says nothing about return structure, pagination, or how many entries to expect.

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?

Front-loads the read tag and resource in one line, then documents the argument compactly. No filler, though the Args block styling is slightly verbose for a single parameter.

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?

For a simple read-only tool the description covers purpose and the single parameter, but with no output schema it should say more about the returned shape of the mapping list. The 'normalized' hint is the only return-value context provided.

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?

Schema coverage is 0% and the single target parameter is undocumented in the schema, so the description carries the full burden and does so: 'Firewall target name from config; omit for the default' explains both meaning and default behavior.

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?

States a specific verb ([READ]) and resource (1:1 NAT mappings), with scope qualifiers (external ↔ internal, normalized) that distinguish it from sibling NAT tools like nat_port_forwards and nat_outbound. It does not name those siblings explicitly, so it stops short of full differentiation.

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 when-to-use, when-not, or alternative selection guidance is given. The reader must infer that this is for 1:1 NAT specifically versus port-forward or outbound NAT from the name alone. The only practical guidance ('omit for the default') is parameter-level, not usage-level.

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