Skip to main content
Glama
tempatsimpanku-pixel

genieacs-nbi-mcp

by tempatsimpanku-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Presets

acs_presets
Read-onlyIdempotent

Lists ACS presets to show which provisions run for which devices, including channel, weight, precondition, and events.

Instructions

List presets (GET /presets): which provisions run for which devices (channel, weight, precondition, events).

Input Schema

NameRequiredDescriptionDefault
skipNoRows to skip, for paging. Use `total` in the result to know how many exist.
sortNoSort as JSON, e.g. {"_lastInform":-1}.
limitNoRows to return (default and maximum come from the server configuration).
queryNoGenieACS query as a JSON object (or JSON string), e.g. {"_id":{"$regex":"ZTE"}} or {"_lastInform":{"$gt":"2026-10-15T00:00:00Z"}}. Operators: $eq $ne $in $nin $gt $gte $lt $lte $exists $and $or $regex.
projectionNoComma separated parameter paths to return, e.g. "_id,_lastInform,InternetGatewayDevice.DeviceInfo.SerialNumber". Strongly recommended: a full device document can be hundreds of KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety behavior is covered structurally. The description adds domain context about what presets contain, but does not describe pagination behavior, default limits, or result shape beyond what the schema implies.

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?

A single front-loaded sentence that names the operation, the endpoint, and the core domain semantics. There is no wasted text or tangential detail.

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?

For a read-only list tool with complete schema descriptions and clear annotations, the definition gives enough context to understand what is being listed. The remaining gap is sibling differentiation and output/result expectations, but the structured fields cover most of the call mechanics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description adds no parameter-specific detail. Baseline 3 is appropriate: the schema already carries the full burden for skip, sort, limit, query, and projection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('List presets') and explains what a preset represents (provisions, devices, channel, weight, precondition, events). It is clearer than most sibling listings but does not explicitly contrast itself with acs_provisions or acs_devices.

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?

There is no explicit guidance on when to use this tool versus alternatives such as acs_provisions or acs_devices. The '(GET /presets)' endpoint hints at read-only listing, but the description leaves usage context entirely implicit.

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