Skip to main content
Glama

set_parameter

Destructive

Set TR-069 parameter values on a CPE device to change configurations such as WiFi SSID or management server URL. Queues the task and sends a connection request for immediate execution.

Instructions

Set one or more TR-069 parameter values on a CPE device through GenieACS. Use this tool to change device configuration such as WiFi SSID, management server URL, periodic inform interval, or any writable TR-069 parameter. The parameter_values argument must be a JSON array of tuples, where each tuple is [parameterPath, value] or [parameterPath, value, xsdType]. Example: [["InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID","MySSID","xsd:string"]]. Valid xsd types include xsd:string, xsd:boolean, xsd:unsignedInt, xsd:int, xsd:dateTime. If the type is omitted, GenieACS infers it from the value. The task is queued and a connection request is sent to the CPE for immediate execution. Returns the raw ACS JSON response confirming the task. Limitations: the CPE must be reachable for immediate execution; otherwise the task remains queued until the next periodic inform. Not all parameters are writable — the CPE will fault if you attempt to set a read-only parameter. Use refresh_parameter or genieacs://device/{id} first to discover valid parameter paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYesThe exact GenieACS device identifier (_id field). Typically in the format OUI-ProductClass-SerialNumber (e.g. "00236A-SmartRG585-SMRT00236a42"). Obtain valid IDs from the genieacs://devices/list resource.
parameter_valuesYesA JSON array of parameter tuples to set. Each tuple is either [path, value] or [path, value, xsdType]. Example: [["Device.WiFi.SSID.1.SSID","NewName","xsd:string"],["Device.ManagementServer.PeriodicInformInterval",300,"xsd:unsignedInt"]]
Behavior5/5

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

Annotations lack behavioral details, but the description fully explains: task queuing, immediate execution via connection request, queuing if unreachable, and fault behavior for read-only parameters. No contradiction with annotations.

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 paragraph of 8 sentences, each sentence adds unique value. It is front-loaded with the main purpose, followed by examples, types, limitations, and alternatives. No wasted words.

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 no output schema, the description explains the return value ('raw ACS JSON response confirming the task'). It covers limitations, prerequisites, and error scenarios. Everything an agent needs is present.

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?

Although schema coverage is 100%, the description adds critical meaning: JSON array of tuples format, example, list of valid xsd types, and inference if type omitted. This goes beyond the schema's parameter descriptions.

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 clearly states the tool's purpose: 'Set one or more TR-069 parameter values on a CPE device through GenieACS.' It specifies the verb (set), resource (parameter values on CPE), and distinguishes it from sibling tools like get_parameter or reboot_device.

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

Usage Guidelines5/5

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

Explicitly states when to use (change device configuration like WiFi SSID) and provides warnings: CPE must be reachable, read-only parameters will fault. Suggests alternatives: 'Use refresh_parameter or genieacs://device/{id} first to discover valid parameter paths.'

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/GeiserX/genieacs-mcp'

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