NetCraze-mcp

by wise108

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_static_host

Remove a static DNS host entry by hostname and save the configuration.

Instructions

Delete static DNS host by name 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>"
    },
    "name": "delete_static_host"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it deletes and saves configuration but does not disclose immediacy, reversibility, or additional side effects. The agent cannot infer behavior beyond the stated action.

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?

The description is a single sentence, which is concise but could benefit from additional context without being verbose. It is front-loaded but too sparse to be highly effective.

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?

Given the simplicity (one parameter, no output schema), the description somewhat covers the purpose and action. However, it lacks details about the effect (e.g., configuration persistence) and does not exploit the opportunity to be more informative.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It says 'by name' implying the 'host' parameter is the name, but adds no format, validation, or examples. The description provides minimal extra meaning beyond the schema.

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?

Description clearly states it deletes a static DNS host by name and saves configuration. The verb 'delete' and resource 'static DNS host' are specific, and it distinguishes from sibling tools like 'add_static_host' and 'list_static_hosts'.

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, and no when-not-to-use scenarios. For instance, it doesn't mention that the host must exist or that changes are permanent.

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