Skip to main content
Glama
Sign In
zte-f680-mcp

zte-f680-mcp

by Picaresco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

zte_modify_port_forward

Update an existing port forwarding rule's name, protocol, ports, and internal host to reconfigure traffic routing.

Instructions

Modifica una regla de port forwarding existente.

Args: index: Indice de la regla (obtenido con zte_get_port_forwards). name: Nuevo nombre de la regla. protocol: "TCP", "UDP" o "TCP+UDP". external_port_start: Puerto externo inicial. external_port_end: Puerto externo final. internal_host: IP interna destino. internal_port_start: Puerto interno inicial. internal_port_end: Puerto interno final.

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": {
      "index": "<index>",
      "name": "<name>",
      "protocol": "<protocol>",
      "external_port_start": "<external_port_start>",
      "external_port_end": "<external_port_end>",
      "internal_host": "<internal_host>",
      "internal_port_start": "<internal_port_start>",
      "internal_port_end": "<internal_port_end>"
    },
    "name": "zte_modify_port_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
indexYes
protocolYes
internal_hostYes
external_port_endYes
internal_port_endYes
external_port_startYes
internal_port_startYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description does not elaborate on behavioral traits beyond stating that it modifies a rule. No mention of side effects, authentication needs, or what happens on failure. The description adds minimal value over annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, uses a clear structure with a purpose statement followed by a parameter list. Every sentence provides value, no unnecessary content.

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?

Given the high parameter count, the description sufficiently explains each parameter and the tool's purpose. An output schema exists, so return values are not required. Lacks details on constraints (e.g., index must exist) but overall complete for selection and invocation.

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

Parameters5/5

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

Schema has 0% description coverage; the description provides clear definitions for all 8 parameters, including that 'index' is obtained from another tool and protocol values. This significantly aids proper invocation.

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?

The description explicitly states 'Modifica una regla de port forwarding existente' (modifies an existing port forwarding rule), which is a specific verb+resource. It clearly distinguishes from siblings like 'add' and 'delete'.

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

Usage Guidelines4/5

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

The purpose is clear from the tool name and description, implying usage for modifying existing rules rather than adding or deleting. However, there is no explicit when-to-use or when-not-to-use guidance, nor mention of prerequisites or constraints.

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

Deploy Server

Other Tools