NetCraze-mcp

by wise108

Overview Schema Source Related Servers Discussions Admin

Python

Remote

add_static_host

Add a static DNS host entry by providing a hostname and IP address, then save the configuration to the router.

Instructions

Add static DNS host and save configuration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "ip": "<ip>"
    },
    "name": "add_static_host"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes
`host`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, and description only mentions 'save configuration' without disclosing whether it overwrites existing entries, requires permissions, or has side effects on runtime DNS resolution.

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?

Single sentence is concise but under-specified; lacks necessary detail for a configuration-changing tool.

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?

No output schema, no annotations, and minimal description leaves out return value, error conditions, and operational context like whether existing entries are updated or rejected.

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?

Schema coverage is 0% and description adds no meaning to the 'host' and 'ip' parameters; it doesn't specify expected formats or constraints.

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?

Clearly states 'Add static DNS host' which is specific verb+resource, and distinguishes from siblings like list_static_hosts and delete_static_host.

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 guidance on when to use this tool vs alternatives, no prerequisites like administrative access or context about when static hosts are needed.

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