Skip to main content
Glama

nucleus_features

Destructive

Track features through their lifecycle, generate cryptographic execution proofs for audit compliance, and mount external MCP servers as composable sub-tools.

Instructions

Track features through their lifecycle, generate cryptographic execution proofs for audit compliance, and mount external MCP servers as composable sub-tools. Use this tool when you need to register a feature, verify code execution, or integrate another MCP server. Do NOT use for task tracking (use nucleus_tasks), memory storage (use nucleus_engrams), or agent spawning (use nucleus_agents). Actions: 'add' creates a feature record with name, description, and initial status. 'update' changes feature status through its lifecycle (proposed/in_progress/done/cancelled). 'validate' marks a feature as verified with evidence. 'list' shows all features. 'get' retrieves one feature by ID. 'search' finds features by keyword. 'generate_proof' creates a cryptographic Ed25519-signed receipt of a code execution for audit compliance (side effect: writes to .brain/proofs/). 'get_proof'/'list_proofs' retrieve stored proofs. 'mount_server' connects an external MCP server as a sub-tool (side effect: spawns a child process). 'discover_tools' lists tools available on a mounted server. 'invoke_tool' calls a tool on a mounted server and returns its result. 'traverse_mount' navigates the mount hierarchy. 'thanos_snap'/'unmount_server' disconnect mounted servers (destructive: kills child process, removes mount config). Prerequisites: .brain directory. Mounting requires the external server command to be installed locally. Returns JSON with {success: boolean, data: object}. Example: {action: 'add', params: {name: 'JWT Auth', description: 'Token-based authentication', status: 'in_progress'}} returns {success: true, data: {feature_id: 'feat_xyz', created: true}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSelect the feature, proof, or mount action. 'add'/'update'/'validate' manage feature lifecycle records. 'search'/'list'/'get'/'list_mounted'/'discover_tools'/'get_proof'/'list_proofs'/'traverse_mount' are read-only queries. 'generate_proof' creates a cryptographic execution receipt. 'mount_server' connects an external MCP server (spawns process). 'invoke_tool' calls a mounted server's tool. 'unmount_server'/'thanos_snap' disconnect and remove mounted servers (destructive: kills process).
paramsNoAction-specific parameters as key-value pairs. add: {name: string (required), description: string (required), status: string (optional, default 'proposed')}. update: {feature_id: string (required), status: string (required, 'proposed'|'in_progress'|'done'|'cancelled'), notes: string (optional)}. get: {feature_id: string (required)}. search: {query: string (required, keyword search)}. validate: {feature_id: string (required), evidence: string (optional)}. mount_server: {name: string (required, display name), command: string (required, executable path), args: string[] (optional, command arguments), env: object (optional, environment variables)}. invoke_tool: {server_name: string (required, mounted server name), tool_name: string (required), arguments: object (optional)}. generate_proof: {action: string (required, what was executed), evidence: object (required, execution artifacts)}. unmount_server: {name: string (required)}. list/list_mounted/discover_tools/get_proof/list_proofs/traverse_mount: no parameters needed.
Behavior5/5

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

Disclosures all side effects: writes to .brain/proofs/ for generate_proof, spawns child process for mount_server, kills process for thanos_snap/unmount_server. Annotations confirm destructiveHint=true, no contradiction.

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 clear sections, front-loaded purpose, and example. Slightly long but every sentence adds value. Could be slightly more concise.

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?

Given no output schema, it includes return format, example, and covers all 16 actions comprehensively with their effects. Sufficient for a complex tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by detailing action-specific required and optional parameters with examples and types beyond schema enums.

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 specifies verb+resource (track, generate, mount) and explicitly distinguishes from sibling tools by naming them (nucleus_tasks, nucleus_engrams, nucleus_agents) and stating what not to use the tool for.

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?

Provides explicit when-to-use scenarios (register feature, verify execution, integrate MCP server) and when-not-to-use with sibling tool names. Also lists prerequisites like .brain directory and external server installation.

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