Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
net_inspect_deviceB

采集单台网络设备的运行状态:CPU/内存/温度/端口/光功率/时延。输入设备编号或 IP。

net_cfg_draftA

根据结构化参数生成华为/思科配置草稿(VLAN、ACL、OSPF),返回配置文本与风险提示,不直接下发。

net_log_analyzeA

分析一段设备日志,按规则识别断链、光衰、通讯超时、弱口令、物理层错包等问题并给出处理建议。

net_ticket_createA

根据告警/故障描述创建运维工单,输出工单号、SLA 时限与初始状态。

net_ticket_updateA

按状态机推进工单:OPEN→ACK→FIXED→CLOSED,非法流转返回 INVALID_TRANSITION。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

Each tool maps to a distinct object/action pair: device inspection, config drafting, log analysis, and ticket create/update. The only mild overlap is between net_inspect_device and net_log_analyze, since both are diagnostic, but their inputs (device ID vs. raw log text) and outputs are clearly separated.

Naming Consistency3/5

All names share a net_ prefix, but the structure is mixed: net_inspect_device is verb-first, while net_cfg_draft, net_log_analyze, net_ticket_create and net_ticket_update are noun-first, and 'cfg' is an abbreviation. Readable and grouped, but not a single predictable pattern.

Tool Count4/5

Five tools is a compact, well-scoped set where each tool has a distinct role in a plausible network-ops workflow. It is slightly thin (single-device inspection, no batch operations) but not under-served for the stated purpose.

Completeness3/5

The surface covers inspect, draft, analyze, and the ticket lifecycle, but has notable gaps: no config apply/push or rollback, no ticket query/list/get beyond creation output, and no device or alert listing. Agents would hit dead ends for read-back and remediation steps.