Skip to main content
Glama
tempatsimpanku-pixel

genieacs-nbi-mcp

by tempatsimpanku-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Faults

acs_faults
Read-onlyIdempotent

List failed ACS sessions and provisioning faults per device or channel, with error code, message, retry count, and timestamps. Use these records to diagnose why an ONT will not provision.

Instructions

List ACS faults (GET /faults): failed sessions or provisions per device/channel, with code, message, retry count and timestamps. Start here for "why does this ONT not provision".

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.
device_idNoOnly entries of this device `_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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds value by enumerating the returned fault fields and the per-device/per-channel scope, which matters since there is no output schema; it doesn't mention paging defaults or result volume, but the schema covers those.

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 sentences, front-loaded with what it returns and immediately followed by the routing hint. No filler.

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?

All optional parameters are fully documented in the schema and the description supplies the missing return-value context (fault fields) since no output schema exists. Only gap is guidance on narrowing large result sets against the other diagnostic siblings.

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 all six parameters are documented with examples and operators, so the description adds nothing beyond it. Baseline 3 per the high-coverage rule.

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 ACS faults') plus the underlying endpoint (GET /faults) and the record contents (code, message, retry count, timestamps). An agent can distinguish it from acs_devices/acs_tasks because faults are framed as failed sessions/provisions, though no sibling is named explicitly.

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?

'Start here for "why does this ONT not provision"' gives a concrete diagnostic trigger for selecting this tool. It stops short of naming alternatives (e.g. when to use acs_tasks or acs_device instead) or stating exclusions.

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