Skip to main content
Glama
Sign In
network-aiops

network-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_optics

Read-only

Read optical transceiver rx/tx power and bias levels per interface or channel to monitor link health and troubleshoot signal problems.

Instructions

[READ] Optical transceiver levels per interface/channel (rx/tx power, bias).

Args: target: Device name from config.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_optics"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the '[READ]' prefix merely restates that annotation. The description does add value by naming the returned measurements (rx/tx power, bias) and the per-interface/channel granularity, but says nothing about behavior on interfaces without optics, error handling, or output shape.

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?

Two short, front-loaded lines with zero filler; the resource and returned fields come before the argument block. The 'Args:' section is efficient, though the bare framing gives it a slightly terse, note-like feel.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with no output schema, the description covers the essentials. It omits what an omitted target does and gives no hint of the return structure or volume, which leaves a real gap given the 0% schema coverage.

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 0%, so the description must carry the parameter burden and it only partially does: 'Device name from config' clarifies the value's source and format. It never explains the null default (does omitting target query all devices?), which is the one ambiguity an agent would actually hit.

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 concrete resource (optical transceiver levels) plus the specific measurements returned (rx/tx power, bias) and the granularity (per interface/channel). No sibling covers optics, so differentiation is effectively automatic, though the description never says so explicitly.

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 when-to-use guidance, no prerequisites, and no pointer to any alternative tool. The agent must infer from the name that this is a diagnostics read used to check transceiver health; nothing in the text states the triggering condition.

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