ops-graph
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.
You are querying the Ops knowledge graph of a (fictional) insurer: servers, applications, databases, teams and monitoring alerts, reconciled from a CMDB, a monitoring export and a service catalog.
Start with describe_schema if you do not know the graph.
Use find_asset to turn a name into an id; tools also accept names directly.
search_docs finds runbook passages and returns the live alerts and dependencies of the assets each passage mentions. Cite the source document when you use it.
Every answer carries its evidence: paths, matching rules, confidence. Report
uncertainandneeds_reviewflags to the user; never present them as facts.read_only_cypher is for questions no other tool answers. It is read-only, times out after 5 s and returns at most 200 rows.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_assetA | Find servers, applications or databases by id, name or any hostname spelling (e.g. 'db01.par'). |
| impact_analysisB | What stops working if this asset stops? Returns every impacted asset with the dependency path that proves it. |
| root_cause_candidatesA | Why is this asset failing? Alerting dependencies, most likely root cause first ('deepest' = nothing below it alerts). |
| decommission_candidatesB | Servers with no live workload, with reasons. Servers whose workload is unknown are listed as 'blocked', never as candidates. |
| compliance_findingsB | Personal data on servers with an unsupported OS or not registered in the CMDB. |
| reconciliation_reportB | Data quality: records reconciliation could not settle, links to review, and how many links each rule made. |
| describe_schemaB | Node and relationship counts and the direction conventions of the graph. |
| search_docsB | Search the runbooks and postmortems (GraphRAG): best passages plus the live state of the assets they mention. |
| read_only_cypherA | Run your own read-only Cypher. Refuses writes, LOAD CSV and dbms/apoc procedures; 5 s timeout; at most 200 rows. |
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 9 tools
Most tools map to distinct analytical questions: impact_analysis, root_cause_candidates, decommission_candidates, compliance_findings, and reconciliation_report each target a different report type. The main overlap is directionality between impact_analysis (downstream) and root_cause_candidates (upstream), but their descriptions explicitly clarify the direction. read_only_cypher is a deliberate catch-all escape hatch rather than a duplicate.
There is a mix of conventions: verb_noun tools (find_asset, describe_schema, search_docs), noun_phrase report tools (impact_analysis, compliance_findings, reconciliation_report), and a bare descriptor (read_only_cypher). Each name is readable and self-explanatory, but no single predictable pattern governs the set.
Nine tools is well within the sweet spot and each tool earns its place, covering a distinct analysis or lookup capability. No redundant or filler tools are present.
The read-only ops-graph surface covers dependency impact, root cause, decommission, compliance, data-quality reconciliation, schema introspection, doc search, asset lookup, and a query escape hatch — a solid lifecycle for read-only analysis. Minor gaps like a dedicated full-asset-detail/property listing exist, but find_asset plus read_only_cypher let agents work around them.