Skip to main content
Glama
0xEkho

Ruckus Virtual SmartZone MCP Server

by 0xEkho

vsz_update_ap

Update an AP's configuration on Ruckus Virtual SmartZone: change name, description, zone, group, location, or GPS coordinates using its MAC address.

Instructions

Update access point configuration.

    Args:
        host: vSZ controller IP or hostname.
        ap_mac: AP MAC address.
        name: New AP name.
        description: New AP description.
        zone_id: Move AP to a different zone (UUID).
        ap_group_id: Assign AP to a different AP group (UUID).
        location: AP location string.
        gps_latitude: GPS latitude.
        gps_longitude: GPS longitude.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
nameNo
ap_macYes
zone_idNo
locationNo
ap_group_idNo
descriptionNo
gps_latitudeNo
gps_longitudeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Update access point configuration' and lists parameters, but does not explain side effects (e.g., whether changes are immediately applied), authentication requirements, or any other behavioral traits. This is a significant gap for a mutation tool.

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?

The description is well-structured with a one-sentence summary followed by an Args block. Each parameter has a concise, non-redundant description. It is slightly long due to 9 parameters, but every line serves a purpose.

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?

The description covers all 9 parameters with semantics and there is an output schema available, but it lacks usage context and behavioral side effects. For an update tool, the description is minimally viable but not comprehensive, as the agent must infer operational considerations.

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?

Schema coverage is 0%, so the description compensates by explicitly describing each parameter's role (e.g., 'Move AP to a different zone (UUID)', 'Assign AP to a different AP group (UUID)'). This adds meaningful context beyond the raw schema, though minor details like GPS units are omitted.

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 opens with 'Update access point configuration,' which clearly states the verb and resource. The name vsz_update_ap and the sibling list (vsz_get_ap, vsz_delete_ap, vsz_reboot_ap) further confirm this tool's specific role, distinguishing it from related AP operations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites such as the AP needing to exist, nor does it contrast with vsz_get_ap, vsz_delete_ap, or vsz_update_zone. The usage context must be inferred entirely from the tool name and description.

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/0xEkho/Ruckus-vSZ-MCP'

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