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

zte-f680-mcp

by Picaresco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

zte_get_wan_status

Read-only

Retrieve WAN status from a ZTE F680 router, including public IP, gateway, DNS, MAC address, connection type, and link uptime.

Instructions

Devuelve IP publica, gateway, DNS, MAC WAN, tipo de conexion y uptime del enlace WAN del router.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by listing the specific fields returned, but does not disclose additional behavioral traits such as response format or any side effects. Since annotations cover safety, a score of 3 is appropriate.

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 a single, well-structured sentence that front-loads the key information. No wasted words; every element is necessary to convey the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and an output schema exists, the description fully explains what data is returned. It covers all relevant aspects for a simple read operation, making it complete for an AI agent to understand.

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?

The tool has no parameters, and schema coverage is trivially 100%. The description does not need to add parameter-level meaning, and it clearly explains the output. With no parameters, the description is sufficient.

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 the tool returns public IP, gateway, DNS, WAN MAC, connection type, and uptime of the router's WAN link. It specifies the verb 'devuelve' (returns) and the resource 'enlace WAN del router', clearly distinguishing it from sibling tools that handle port forwarding, device info, etc.

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 description implies usage for retrieving WAN status, but provides no explicit guidance on when to use this tool versus alternatives like zte_get_device_info or other status tools. No when-not-to-use or prerequisite information is given.

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