Skip to main content
Glama

manage_preset

Destructive

Create, update, or delete GenieACS presets to define automatic configuration rules for CPE devices based on precondition filters.

Instructions

Create, update, or delete a GenieACS preset. Presets define automatic configuration rules that are applied to CPE devices matching a precondition filter. Use action="put" to create or overwrite a preset, providing the full JSON body with weight, precondition, and configurations. Use action="delete" to remove a preset by name. A preset body should contain: weight (integer priority), precondition (a stringified MongoDB-style JSON query, e.g. "{"_tags":"office"}"), and configurations (array of objects with type "value", "provision", "add_object", or "delete_object"). Example body: {"weight":0,"precondition":"{"_tags":"test"}","configurations":[{"type":"provision","name":"myScript"}]}. Preset names cannot contain dots. Use genieacs://presets/list to view existing presets before making changes. Limitations: changes take effect on the next CPE inform, not immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe operation to perform: "put" to create or update a preset, "delete" to remove it.
bodyNoThe full JSON preset document (required for action="put", ignored for "delete"). Must contain weight, precondition, and configurations fields.
nameYesThe preset name (used as the identifier in the URL). Cannot contain dots.
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description confirms by stating it can delete presets. The description adds valuable context: changes take effect on next CPE inform, not immediately. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph, but it is well-organized and front-loads the purpose. Every sentence contributes useful information; however, it could be slightly more concise by removing some redundancy.

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?

Given no output schema and three parameters (two required), the description covers usage, constraints (name cannot contain dots), example, and limitations (deferred effect). It is complete for an agent to use the tool correctly.

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 100%, but the description enriches parameter understanding by detailing the body structure (weight, precondition, configurations) and providing a concrete example. This adds meaning beyond the schema alone.

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: 'Create, update, or delete a GenieACS preset.' It explains what presets are and distinguishes itself from sibling tools (e.g., connection_request, delete_task). The verb 'manage' combined with resource 'preset' is specific and unambiguous.

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?

The description explicitly outlines when to use action='put' vs 'delete', provides an example body, and recommends viewing existing presets via genieacs://presets/list. It does not explicitly state when not to use the tool, but the context is clear.

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