Skip to main content
Glama
AIops-tools

fabric-aiops

update_network_vlan

Update a VLAN's attributes (name, subnet, appliance IP, group policy, DHCP handling) on a Meraki network, capturing prior values for undo and supporting dry-run preview.

Instructions

[WRITE][risk=medium] Update an appliance VLAN, capturing its prior values.

Captures the changed keys' prior values before the change (undo restores
them). Pass dry_run=True to preview.

Args:
    network_id: Meraki network id.
    vlan_id: VLAN id to update.
    attrs: Attributes to set — allowed keys: name, subnet, applianceIp,
        groupPolicyId, dhcpHandling.
    dry_run: If True, preview without changing.
    target: Target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attrsYes
targetNo
dry_runNo
vlan_idYes
network_idYes
Behavior3/5

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

Discloses undo capture and dry_run behavior. No annotations provided, so description carries burden; lacks failure modes, permissions, or idempotency details.

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?

Well-structured with docstring format. Every sentence adds value; no wasted words. Front-loaded with risk indicator and capture behavior.

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?

Covers all parameters and key behavioral traits. No output schema, so return value not described; otherwise complete for a mutation tool.

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?

Describes allowed keys for attrs, explains dry_run, and lists required parameters. Compensates fully for 0% schema coverage by providing constraints not in schema.

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?

Description clearly states 'Update an appliance VLAN' and highlights unique behavior 'capturing its prior values'. Distinguishes from sibling list/read tools.

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?

Mentions dry_run for preview and undo capability, giving context on when to use safely. No explicit when-not-to-use but sibling set implies mutation purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Fabric-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server