Skip to main content
Glama

nucleus

by io.github.eidetic-works

Agent Spawning

nucleus_agents

Agent spawning, critic, swarm, memory, ingestion & dashboard tools.

Actions: spawn_agent - Spawn Ephemeral Agent. params: {intent, execute_now?, persona?, confirm?}. HITL: requires confirm=true. apply_critique - Apply critique fixes. params: {review_path} orchestrate_swarm - Start multi-agent swarm. params: {mission, agents?} search_memory - Search long-term memory. params: {query} read_memory - Read memory category. params: {category} respond_to_consent - Respond to respawn consent. params: {agent_id, choice?} list_pending_consents - List agents awaiting consent critique_code - Run Critic review. params: {file_path, context?} fix_code - Auto-fix code. params: {file_path, issues_context} session_briefing - Get session briefing. params: {conversation_id?} register_session - Register session focus. params: {conversation_id, focus_area, role?, tier?, charter_path?, parent_session?}. Tier ∈ {opus,sonnet,haiku}; role must start with tier prefix. handoff_task - Hand off task. params: {task_description, target_session_id?, priority?} ingest_tasks - Ingest tasks. params: {source, source_type?, session_id?, auto_assign?, skip_dedup?, dry_run?} rollback_ingestion - Rollback ingestion. params: {batch_id, reason?} ingestion_stats - Get ingestion statistics dashboard - Enhanced dashboard. params: {detail_level?, format?, include_alerts?, include_trends?, category?} snapshot_dashboard - Create dashboard snapshot. params: {name?} list_dashboard_snapshots - List snapshots. params: {limit?} get_alerts - Get active alerts set_alert_threshold - Set alert threshold. params: {metric, level, value}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

B3.2/5.0
Behavior2/5

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

The description does not disclose behavioral traits beyond listing actions and their parameters. The annotations provide readOnlyHint=false and destructiveHint=false, but several listed actions (e.g., rollback_ingestion, set_alert_threshold, spawn_agent) are potentially destructive, creating an annotation contradiction. No clarity on permissions, side effects, or irreversible changes is provided.

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 a well-structured list of actions with brief parameter summaries. While long (20 actions), it avoids extraneous text. However, a more compact format (e.g., table) could improve readability; current form is acceptable for a router tool.

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

Completeness3/5

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

Given the tool's complexity (many sub-actions) and generic schema (action+params), the description covers sub-action names and parameters but lacks examples, return values, or detailed behaviors. The existence of an output schema mitigates some gaps, but the description could do more to explain usage patterns and edge cases.

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

Parameters3/5

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

The input schema has only 'action' and 'params' with no descriptions (0% coverage), but the description lists each action's parameters (e.g., intent, review_path). This adds meaning by naming the params, but lacks types, formats, or detailed semantics, leaving ambiguity (e.g., what is 'intent'? 'file_path'? ).

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

Purpose4/5

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

The description clearly states 'Agent spawning, critic, swarm, memory, ingestion & dashboard tools' and lists 20 sub-actions, providing a broad but specific purpose. It distinguishes from sibling nucleus_* tools by enumerating its capabilities, though it lacks a single verb-resource focus.

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

Usage Guidelines3/5

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

The description implies usage for the listed sub-actions (e.g., spawning agents, critiquing code) but does not provide explicit when-to-use or when-not-to-use guidance compared to sibling tools. No alternatives or exclusions are mentioned, relying on the action list to convey scope.

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

All nucleus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation4/5

Tools are grouped by domain with detailed descriptions, but some overlap exists (e.g., multiple relay-related tools like nucleus_relay, nucleus_relay_subscribe, nucleus_next_message). Overall, most tools have distinct purposes, and descriptions help disambiguate.

Naming Consistency5/5

All tool names follow the 'nucleus_' prefix with a consistent noun-like second part (e.g., nucleus_agents, nucleus_audit, nucleus_delegate). Even compound names like nucleus_lane_feedback maintain the pattern, with no mixing of conventions.

Tool Count3/5

With 28 tools, the count is on the higher end but still justifiable given the broad scope of an agent operating system. The tools cover many necessary functions, though the set could be slightly trimmed for focus.

Completeness4/5

The tool surface covers most aspects of an agent OS: agents, audit, delegation, memory, features, federation, governance, infra, lanes, messaging, orchestration, plans, relay, routing, sessions, slots, sync, tasks, telemetry. Minor gaps like a dedicated config tool are absent but not critical.

Resources