nimbus
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchIndexA | Search the Nimbus local index across all connected services (Drive, GitHub, Slack, Jira, etc.). Returns ranked items. Optionally filter by service or itemType. |
| getConnectorStatusA | List Nimbus connector health and sync state for every configured connector. |
| getRecentIncidentsA | List recent incidents from the local index (most recent first). Optionally filter by service. |
| getRecentPullRequestsA | List recent pull requests from the local index (most recent first). Each item carries its state (open/closed/merged) under meta.state when the connector recorded it — filter on that; the index cannot pre-filter by PR state. |
| getRecentDeploymentsA | List recent deployments from the local index (most recent first). Optionally filter by service. |
| getDoraMetricsB | Get DORA metrics (deployment frequency, lead time for changes, change failure rate, MTTR) for a configured service. |
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 6 tools
Each tool has a distinct primary purpose: general search, connector status, recent PRs, deployments, DORA metrics, and incidents. There is some conceptual overlap between searchIndex and the getRecent* helpers, but the descriptions clarify ranked search vs. time-ordered lists.
Tools consistently use camelCase with a 'get' prefix for most queries, and the getRecent* grouping is a strong pattern. The one deviation is searchIndex, which lacks a 'get' prefix but still follows a readable verb_noun structure.
Six tools is well within the ideal 3-15 range for a focused read-only data access server. Each tool covers a distinct, useful capability without bloat.
The surface covers the core read operations for the index: search, connector health, recent item lists, and DORA metrics. Minor gaps like item detail retrieval or additional item types are mitigated by the generic searchIndex tool, which can access any indexed entity.