Skip to main content
Glama

update_address_list_entry

Idempotent

Modify an existing IPv4 or IPv6 address list entry identified by its current list name and address, including comment, timeout, disabled state, or a new list name.

Instructions

Updates an address list entry, located by its current list name and address.

Notes: Pass "" to clear comment or timeout. A change is confirmed on the device before success is reported.

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": {
      "family": "<family>",
      "list_name": "<list_name>",
      "address": "<address>"
    },
    "name": "update_address_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
familyYes
addressYes
commentNo
timeoutNo
disabledNo
list_nameYes
new_list_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.22.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds a genuinely non-obvious behavior beyond them: changes are verified on the device before success is reported, implying a round-trip confirmation and failures surfacing as errors. It does not say what happens to fields left null (unchanged vs cleared), which is the main remaining ambiguity.

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?

Front-loaded single sentence followed by a short Notes block; every line carries information and there is no filler. Minor awkwardness in the nested leading whitespace of the notes, but nothing is redundant.

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?

Output schema and annotations absorb the return-value and safety burden, and the device-confirmation note covers atomicity. However, for an 8-parameter mutation tool at 0% schema coverage, an agent still cannot tell which fields are updatable or how new_list_name/disabled behave, so the definition is adequate but incomplete.

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 carry 8 parameters and it explains only that list_name and address form the locator plus the empty-string convention for comment/timeout. It says nothing about device, family (the only enum), disabled, or new_list_name — the rename parameter — leaving the most consequential parameter undocumented in both schema and prose.

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?

States a specific verb and resource ("Updates an address list entry") and, unusually, the identity key ("located by its current list name and address"), which tells an agent exactly how the target is addressed. This distinguishes it from siblings such as enable_address_list_entry, disable_address_list_entry, and remove_address_list_entry without naming them.

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?

No explicit when-to-use or when-not-to-use guidance versus create/remove/enable/disable siblings. The note about passing "" to clear comment or timeout implies one usage case (field erasure rather than entry removal), which is the only routing hint present.

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