Skip to main content
Glama
tempatsimpanku-pixel

genieacs-nbi-mcp

by tempatsimpanku-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Firmware / config files

acs_files
Read-onlyIdempotent

List firmware images and vendor configuration files stored in an ACS, returning filename, file type, OUI, product class, and version metadata for inventory checks.

Instructions

List files stored in the ACS (GET /files): firmware images and vendor config files with filename, fileType, OUI, productClass and version. Metadata only; file contents are not downloadable here.

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.
filenameNoExact filename (matches `_id`).
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real behavioral context by clarifying that results are metadata only and that binary contents cannot be fetched here — a genuine expectation an agent would otherwise have for a firmware listing. It stops short of noting paging defaults or result size behavior.

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?

Two tightly written sentences: identity and endpoint first, returned shape second, scope limitation last. No filler, nothing repeated from the schema.

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?

With six optional parameters, no output schema, and no required inputs, the description appropriately spends its words on the returned fields and the metadata-only constraint. A note on default/maximum result size or paging would round it out, but that is already partially covered in the schema text.

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%, with skip/limit/sort/query/projection all documented inline, so the baseline is 3. The description only hints at filterable attributes (filename, fileType, OUI, productClass, version) as returned fields rather than explaining how to filter on them via query/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?

States a specific verb and resource ("List files stored in the ACS") plus the underlying endpoint GET /files and the fields returned (filename, fileType, OUI, productClass, version). The resource is clearly distinct from the device/task/fault/preset siblings, though no sibling is named explicitly for the download-oriented use case it excludes.

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

Usage Guidelines3/5

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

Usage is only implied: the resource name indicates when to reach for it, and "file contents are not downloadable here" excludes one expectation, but there is no explicit when-to-use statement or pointer to an alternative tool for retrieving file contents or firmware.

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