Skip to main content
Glama

nucleus_infra

Monitor infrastructure health and GCP services, track file changes, and generate strategic reports for operational awareness.

Instructions

Monitor infrastructure health, manage Google Cloud Platform services, track file changes across your project, and generate strategic planning reports. Use this tool when you need operational awareness of your development environment, GCP service status, or strategic recommendations. Do NOT use for code-level tasks (use nucleus_tasks), memory (use nucleus_engrams), or deployment orchestration (use nucleus_sync with deploy actions). Actions: 'file_changes' lists recently modified files in the project directory with timestamps and sizes (read-only, useful for detecting unexpected modifications). 'gcloud_status' checks Google Cloud Platform availability and incident status. 'gcloud_services' lists all enabled GCP services for a project (requires project_id). 'list_services' shows locally running services detected on common ports. 'status_report' generates a formatted markdown or JSON summary of brain health, task status, session state, and frontier metrics. 'synthesize_strategy' analyzes accumulated data (engrams, patterns, metrics) and recommends strategic actions. 'optimize_workflow' suggests process improvements for a named area. 'manage_strategy' reads and writes strategy documents to .brain/strategy/ (side effect: creates or modifies files). 'update_roadmap' modifies roadmap items in .brain/roadmap.json (side effect: modifies file). 'scan_marketing_log' analyzes marketing-related log entries. Prerequisites: .brain directory. GCloud actions require 'gcloud' CLI installed and authenticated via 'gcloud auth login'. Returns JSON with {success: boolean, data: object}. Example: {action: 'file_changes', params: {since: '24h', path: 'src/'}} returns {success: true, data: {changes: [{path: 'src/app.py', modified: '2026-04-04T10:00:00Z', size: 1234}]}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSelect the infrastructure, cloud, or strategy action. 'file_changes'/'gcloud_status'/'gcloud_services'/'list_services'/'status_report' are read-only queries. 'scan_marketing_log' analyzes log data. 'synthesize_strategy'/'optimize_workflow' generate recommendations without side effects. 'manage_strategy' reads or writes strategy documents to disk. 'update_roadmap' modifies the roadmap file.
paramsNoAction-specific parameters as key-value pairs. file_changes: {since: string (optional, ISO date like '2026-04-01' or relative like '24h'|'7d', default '24h'), path: string (optional, directory to scan, default project root)}. gcloud_services: {project_id: string (required, GCP project ID, e.g. 'my-project-123')}. status_report: {format: string (optional, 'markdown'|'json', default 'markdown'), scope: string (optional, 'full'|'summary', default 'full')}. update_roadmap: {item: string (required, roadmap item name), status: string (required, new status value), notes: string (optional)}. optimize_workflow: {target_area: string (required, area to analyze, e.g. 'testing'|'deployment'|'code_review')}. manage_strategy: {operation: string (required, 'read'|'write'), key: string (optional, strategy document name), value: string (optional, content for write)}. gcloud_status/list_services/scan_marketing_log/synthesize_strategy: no parameters needed.
Behavior4/5

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

The description discloses which actions are read-only (e.g., 'file_changes'/'status_report') and which have side effects (e.g., 'manage_strategy' creates/modifies files). It also notes the return format ({success, data}). Annotations are consistent (readOnlyHint: false fits the mix of actions).

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?

The description is thorough and well-structured: starts with overall purpose, lists actions, prerequisites, return format, and ends with an example. Every sentence adds value. Could be slightly more concise, but the detail is justified given the tool's complexity.

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

Completeness4/5

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

Given the tool's many actions and nested parameters, the description is highly complete. It covers all actions, their behavior, prerequisites, and return format. No output schema exists, but the description provides the JSON structure. Minor omissions: no explanation of 'scan_marketing_log' beyond 'analyzes marketing-related log entries'; still, overall very good.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with descriptions for both parameters. The description adds significant additional semantics: it explains each action's purpose, lists sub-parameters for params with formats and defaults, and provides an example. This goes beyond schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Monitor infrastructure health, manage Google Cloud Platform services, track file changes across your project, and generate strategic planning reports.' It distinguishes itself from siblings by explicitly listing what not to use it for and suggesting alternative tools (nucleus_tasks, nucleus_engrams, nucleus_sync).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool ('when you need operational awareness...') and when not to use it ('Do NOT use for code-level tasks...'). It also lists prerequisites (gcloud CLI, .brain directory) and the return format, helping agents determine appropriateness.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eidetic-works/nucleus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server