Skip to main content
Glama

nucleus_orchestration

Destructive

Get strategic awareness of active work through satellite overviews, commitment tracking, open loop management, pattern detection, and data export.

Instructions

Get strategic awareness of all active work through satellite overviews, commitment tracking, open loop management, pattern detection, and data export. Use this tool when you need a high-level view of project state, want to track promises made during sessions, identify recurring patterns, or export data. Do NOT use for individual task CRUD (use nucleus_tasks), session management (use nucleus_sessions), or slot-based sprint execution (use nucleus_slots). Actions: 'satellite' returns a comprehensive bird's-eye view of tasks, sessions, commitments, health scores, and frontier status — the best starting point for understanding current state. 'scan_commitments' extracts promises and action items from session transcripts. 'list_commitments' shows all tracked commitments. 'close_commitment' marks a commitment as fulfilled with a resolution note. 'commitment_health' scores how well commitments are being met. 'open_loops' shows unfinished work items that need closure. 'add_loop' registers something that needs follow-up. 'patterns' detects recurring themes across sessions and tasks. 'metrics' shows system-wide statistics (tool usage, event counts, memory growth). 'export' dumps data in json/csv/markdown format. 'weekly_challenge' generates a focused challenge based on recent activity. 'archive_stale' removes commitments older than N days (destructive: deletes records). Prerequisites: .brain directory with session history for best results. Returns JSON with {success: boolean, data: object}. Example: {action: 'satellite'} returns {success: true, data: {tasks: {total: 12, in_progress: 3}, sessions: {active: 'sess_abc'}, commitments: {open: 5, overdue: 1}}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSelect the orchestration action. 'satellite'/'list_commitments'/'commitment_health'/'open_loops'/'patterns'/'metrics' are read-only overviews. 'scan_commitments' analyzes session transcripts to extract promises. 'close_commitment' resolves a tracked commitment. 'add_loop' registers an open item. 'export' generates formatted output. 'weekly_challenge' creates a focus challenge. 'archive_stale' removes old commitments (destructive: deletes data).
paramsNoAction-specific parameters as key-value pairs. close_commitment: {commitment_id: string (required), resolution: string (required, how the commitment was fulfilled)}. add_loop: {description: string (required, what needs follow-up), context: string (optional, background info), priority: string (optional, 'high'|'medium'|'low', default 'medium')}. export: {format: string (optional, 'json'|'csv'|'markdown', default 'json'), target: string (optional, file path to write to)}. archive_stale: {days_old: integer (required, commitments older than this many days are removed)}. scan_commitments: {session_id: string (optional, defaults to current session)}. satellite/list_commitments/commitment_health/open_loops/patterns/metrics/weekly_challenge: no parameters needed.
Behavior5/5

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

Annotations indicate destructiveHint: true; description confirms archive_stale is destructive. Highlights read-only nature of many actions. No contradictions with annotations.

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?

Well-structured with action list and examples, though somewhat lengthy. Front-loaded with purpose and usage guidelines.

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

Completeness5/5

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

Covers all 12 actions with their effects, parameter details, and return shape. No output schema but description explains JSON response format with example.

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?

Schema description coverage is 100%, but description adds extra value by specifying required fields and optional defaults for each action (e.g., close_commitment requires commitment_id and resolution).

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 defines the tool's purpose: providing strategic awareness through satellite overviews, commitment tracking, and pattern detection. It distinguishes from sibling tools by explicitly excluding individual task CRUD, session management, and slot sprint execution.

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?

Explicitly states when to use (high-level view, track promises, patterns, export) and when not to use (nucleus_tasks, nucleus_sessions, nucleus_slots). Also mentions prerequisites (.brain directory) for best results.

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