Skip to main content
Glama

nucleus

by io.github.eidetic-works

Cross-Agent Sync

nucleus_sync

Sync, artifact, trigger & deploy management for multi-agent coordination.

Actions: identify_agent - Register agent identity. params: {role, provider, session_id} (per ADR-0005 §D1) OR legacy {agent_id, environment, role?} (coerced per §D5 until end of Cycle C+2) sync_status - Check current multi-agent sync status sync_now - Manually trigger sync. params: {force?} sync_auto - Enable/disable file watching. params: {enable} sync_resolve - Resolve a file conflict. params: {file_path, strategy?} read_artifact - Read an artifact file. params: {path} write_artifact - Write to an artifact file. params: {path, content} list_artifacts - List artifacts. params: {folder?} trigger_agent - Trigger an agent via event. params: {agent, task_description, context_files?} get_triggers - Get all defined neural triggers evaluate_triggers - Evaluate triggers for an event. params: {event_type, emitter} start_deploy_poll - Start monitoring a Render deploy. params: {service_id, commit_sha?} check_deploy - Check deploy poll status. params: {service_id} complete_deploy - Mark deploy complete. params: {service_id, success, deploy_url?, error?, run_smoke_test?} smoke_test - Run a smoke test. params: {url, endpoint?} shared_read - Read shared state. params: {key} shared_write - Write shared state. params: {key, value, agent_id?} shared_list - List all shared state keys notify - Send notification to all channels. params: {title, message, level?} list_channels - List configured notification channels add_channel - Add a channel. params: {channel_type, webhook_url?} test_channel - Test a channel. params: {channel_name?} relay_post - Post message to another session type (Cowork↔Claude Code). params: {to, subject, body, priority?, context?, sender?, to_session_id?, from_session_id?, in_reply_to?, task_id?} relay_inbox - Read messages for current session type. params: {unread_only?, limit?, recipient?, session_id?, task_id?} task_comment_add - Post a task-scoped comment (coordination during task execution). params: {task_id, message, sender, subject?, priority?, in_reply_to?} task_comment_list - List all comments for a task. params: {task_id, limit?} declare_posture - Declare agent role + approach (pending operator approval). params: {role, approach?, agent_id?, delegation_targets?} approve_posture - Approve the declared posture (operator only). params: {approved_by?} get_posture - Get current posture. params: {} clear_posture - Clear current posture. params: {} relay_ack - Mark a relay message as read. params: {message_id, recipient?, session_id?} relay_status - Get relay mailbox status across all session types relay_clear - Clean up old relay messages. params: {recipient?, older_than_hours?} relay_log_event - Log a fire/skip event. params: {event, side, subject, tags?, match_reason?, priority?, message_id?, in_reply_to?} relay_skip_review - List recent unclassified skips. params: {limit?} relay_classify_skip - Classify a skip event. params: {ts, subject, classification, note?} relay_event_stats - Compute override + skip rates from event_log.jsonl marketplace_search - Search registered capability cards. params: {tags?, min_tier?, limit?} marketplace_whoami - Get caller's address, tier, reputation. params: {role?} marketplace_can_call - Pre-flight permission check. params: {caller, target} marketplace_recommend - Recommend agents by task description. params: {task, top_k?} marketplace_dashboard - Aggregated health snapshot. params: {} marketplace_history - Reputation event timeline for an address. params: {address, limit?} marketplace_promote - Admin: manually set address tier. params: {address, new_tier, caller?} marketplace_quarantine - Admin: flag address quarantined. params: {address, caller?, reason?} marketplace_audit - Replay admin_actions.jsonl with filters. params: {caller?, target?, action_type?, since_timestamp?, limit?, offset?} marketplace_compare - Head-to-head comparison of two addresses. params: {a, b} marketplace_trends - Tier distribution trend over N days. params: {days?} marketplace_alert - Subscribe to alert rules. params: {subscriber, target, event_types?} marketplace_export - Full registry snapshot (read-only). params: {} marketplace_diff - Diff two registry snapshots. params: {snapshot_a, snapshot_b} marketplace_subscribe - Subscribe to tier-change events. params: {subscriber, target?, event_types?} marketplace_unsubscribe - Remove subscription. params: {subscriber, target?} marketplace_subscriptions - List subscriptions. params: {subscriber?} marketplace_federation_proxy - Proxy an action to a remote federation brain. params: {target_brain, action, payload?} marketplace_federation_register - Register local brain as a federated capability card. params: {address, capabilities?, display_name?, tags?} marketplace_federation_sync - Force federation sync and reconcile marketplace registry. params: {}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are present (all false) but minimal. The description does not add behavioral context beyond listing sub-actions and their parameters. It fails to disclose whether specific sub-actions are destructive, require authentication, or have side effects, which is a significant gap for a tool with write operations like write_artifact and trigger_agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long (50+ lines) and lacks hierarchical structure or a concise summary. Important information is buried in a flat list, making it hard for an AI agent to parse quickly. While detailed, it is not efficiently organized.

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, minimal schema, and an output schema that is not visible), the description provides a broad overview but lacks depth on return values, error handling, and when to use each sub-action. It is adequate but leaves gaps for an agent to fill.

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 only defines 'action' and 'params', with 0% schema description coverage. The description compensates by listing parameters for each sub-action, though some are terse (e.g., 'enable' without type). This adds significant meaning beyond the schema, but misses explicit types, defaults, or constraints.

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 title 'Cross-Agent Sync' and the leading sentence clearly state the tool's domain: sync, artifact, trigger, and deploy management for multi-agent coordination. The long list of sub-actions distinguishes it from sibling tools, though some sub-actions (e.g., relay, marketplace) may overlap with other tools, creating potential ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like nucleus_relay or nucleus_agents. It does not state prerequisites, conditions, or exclusions for the various sub-actions, leaving the agent to infer usage context.

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