Skip to main content
Glama
Sign In
zte-f6600p

zte-f6600p

by brunofin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

router_get_dhcp

Read-onlyIdempotent

Read current DHCP settings from the ZTE F6600P router without modifying them, enabling safe inspection of LAN configuration.

Instructions

Read current DHCP settings without changing them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The phrase 'without changing them' restates readOnlyHint rather than adding new context such as whether the router must be reachable or what the response contains, so the description adds little beyond the annotations.

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?

One short sentence, front-loaded with the action and resource, with no wasted preamble. The trailing clause 'without changing them' is largely redundant with readOnlyHint, which keeps it just below full marks.

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?

This is a simple zero-parameter read with a complete annotation set, and there is no output schema requiring return-value explanation. The description is nearly sufficient; only a hint about what DHCP settings are returned or the sibling relationship would make it fully complete.

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 takes zero parameters, so there is no parameter meaning for the description to convey; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs.

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?

States a specific verb (read) and a specific resource (current DHCP settings), which distinguishes it from resource siblings like router_get_wifi. It does not differentiate from the generic router_read or router_soap_read readers, so the sibling separation is only partial.

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?

Usage is only implied by the resource name: an agent infers it should call this when it needs DHCP configuration. There is no explicit when-to-use statement and no mention of the natural alternative, router_set_dhcp_range, which is the mutation counterpart for the same resource.

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