Skip to main content
Glama

net_cfg_draft

Generates Huawei or Cisco configuration drafts for VLAN, ACL, and OSPF tasks from structured parameters, returning config text and risk warnings without deploying changes.

Instructions

根据结构化参数生成华为/思科配置草稿(VLAN、ACL、OSPF),返回配置文本与风险提示,不直接下发。

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": {
      "platform": "<platform>",
      "task": "<task>",
      "spec": "<spec>"
    },
    "name": "net_cfg_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes任务参数:vlan={vlanId,name,ports[]} acl={aclNumber,permit[],deny[]} ospf={processId,area,networks[]}
taskYes配置任务
platformYes设备平台

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It clearly discloses the key safety property: the tool generates drafts and does not push configuration, and it discloses the return contract: configuration text plus risk hints. It omits details such as whether drafts are persisted anywhere or which validation or errors can occur, but the critical non-mutating behavior is stated well.

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?

This is a single dense sentence that is front-loaded with the core action and ends with the crucial non-deployment constraint. It is efficient, though the long Chinese sentence packing four clauses is somewhat harder to scan than bulleted structure would be.

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 moderately complex tool that has a nested spec object, the definition gives the purpose, the inputs by task family, the output content, and the safety boundary. It does not describe the risk-hint format or the failure modes, and there is no output schema, but the essentials an agent needs to call the tool are present.

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%, and the enums for platform and task are documented in the schema. The description only restates the categories (VLAN, ACL, OSPF) without adding syntax or format meaning beyond what the schema already provides, so this is the baseline.

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?

The description names a specific verb and resource: generate Huawei/Cisco configuration drafts for VLAN, ACL, and OSPF, returning config text plus risk hints. This is a clear purpose, but the description never differentiates it from the sibling tools (inspect, log, ticket), so it does not fully establish when to choose this tool over another.

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

Usage Guidelines3/5

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

The phrase '不直接下发' implies that the tool should be used to preview before deployment, which gives useful context, but the description does not explicitly say when to use this tool rather than another tool, nor does it specify prerequisites or exclusions. The guidance exists only by implication.

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