aiops-field-notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_llm_costA | Price a workload across current frontier and open-weights models. Give tokens per request and monthly request volume; returns cost per request and per month for every model, cheapest first, with the caveats that move the number (batch discounts, prompt caching, intro pricing that expires). |
| check_vram_fitA | Work out whether an open-weights model fits on a given GPU. Takes parameter count in billions, quantisation bit width and context length; returns weights + KV cache + overhead in GB and which common cards (and Macs) have room. |
| audit_mcp_configA | Review an MCP client config before you trust it. Paste the JSON from .mcp.json, claude_desktop_config.json or any equivalent and it flags unpinned packages that auto-update, secrets written in plaintext, filesystem roots scoped to the whole home directory, shell entrypoints, privileged containers, credentials on the command line, unauthenticated or plain-HTTP remote servers, and database access that is not read-only — each with the fix. Nothing is read from disk; pass the text. |
| lookup_mcp_serverA | Look up an MCP server in the curated AIOps Field Notes directory: what it connects to, who maintains it, and whether it is a reference, vendor or community server. Search by name, capability or category. An unlisted server is not condemned — the answer says how to vet it yourself. |
| explain_config_diffA | Explain what changed between two network device config snapshots, in plain English. Works on EdgeOS, MikroTik RouterOS, OPNsense, Cisco IOS-style and EdgeSwitch configs: strips volatile lines, groups changes by config section, and tags each with a risk level and why it matters (security, routing, access, connectivity). Deterministic — no model call, nothing leaves the machine. |
| check_config_complianceA | Run a CIS/PCI starter pack over one network device config: telnet disabled, SSH enabled, no default SNMP community, remote logging, time sync, login banner, hashed credentials, a firewall or ACL, and idle timeout. Deterministic regex checks with framework references, so two reviewers get the same result. |
| latest_field_noteA | The most recent This Week in AIOps episodes — what shipped in models, agents and MCP, and what it means for the systems you run. The only tool here that touches the network; it reads a public RSS feed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose: model cost estimation, GPU fit, RSS news, MCP config auditing, MCP server lookup, config diffing, and compliance checking. Even the two network config tools are cleanly separated by action (diff vs compliance), and the two MCP tools operate on different objects (client config vs server directory).
Six of seven tools follow a clear verb_noun snake_case pattern: estimate_llm_cost, check_vram_fit, audit_mcp_config, lookup_mcp_server, explain_config_diff, check_config_compliance. latest_field_note is the one outlier since it is a noun phrase rather than an imperative verb, but it still uses the same snake_case convention.
Seven tools is a well-scoped set for a field-notes oriented MCP server. Each tool addresses a distinct practical need without bloat or redundancy.
The toolkit covers its main workflows well: model selection has cost and VRAM checks, MCP sanity has audit and lookup, and network config has diff and compliance. Minor gaps exist, such as latest_field_note only fetching the most recent item and no way to submit servers to the directory or auto-fix audit findings, but these do not create dead ends.