Data Agent Creation Tools - Genesis Computing

Overview

Tool Name

make_baby_bot

Purpose

The make_baby_bot toolset lets you create, configure, deploy, and administer purpose-built data agents. Define instructions, select implementations, assign tools and reusable knowledge bases, manage permissions, and roll out bots to Slack or other environments.

Key Features & Functions

Create Specialized Agents

Spin up new bots with clear instructions and a chosen model implementation.

Curate Tool Access

Grant or remove capabilities so each bot has only what it needs.

Deploy to Slack

Connect data agents to Slack with controlled access to users or channels.

Admin & Governance

List, monitor, update, and retire bots with auditable controls.

Evolve Implementations

Switch engines or providers as requirements change.

Name and scope each data agent narrowly. Fewer tools and focused instructions produce safer, more predictable behavior.

GenesisAuditor’s definition is managed by Genesis. Definition-changing calls in this toolset fail for that agent; see the GenesisAuditor guide for the behavior and what remains configurable.

Input Parameters for Each Function

`make_baby_bot`

Parameters

Name	Definition	Format
bot_id	Unique, case-sensitive id in the format `bot_name-xxxxxx` (6 letter code). `Eve` and `eve` are different agents. Genesis rejects a new id that differs from an existing agent only by letter case.	String
bot_name	Human friendly data agent name.	String
bot_intro	Optional short one-line description shown in agent lists and the overview. Keep it at 500 characters or fewer; if omitted, no description is set.	String
bot_instructions	System instructions. Maximum length 250,000 characters.	String
bot_implementation	Runtime LLM engine for the agent: `openai`, `azureopenai`, `cortex`, `databricks`, or `litellm`. LiteLLM sub-provider inputs such as `litellm_anthropic` normalize to `litellm`.	String
available_tools	(Legacy) Comma separated tool group names to grant. Prefer `default_tool_groups` plus `tool_access_mode`/`tool_access_list`; legacy values are migrated into the durable context defaults.	String
knowledge_bases	Registered knowledge base IDs to assign at creation time. Accepts a list, JSON array string, or comma-separated string.	String or Array of strings
activate_slack	Set `Y` to enable Slack deployment, `N` to disable.	String
slack_access_open	`true` for open to all, `false` for allow list.	Boolean
runner_id	Server identifier for hosting (if applicable).	String
confirmed	Extra confirmation flag used only when prompted by the system.	String

Knowledge bases are different from raw document indexes. First register the reusable bundle with Knowledge Base Admin Tools, then pass its knowledge_base_id values here.

Case-sensitive agent IDs. Thread storage paths and metadata caches key off the exact bot_id string stored in BOT_SERVICING. On case-insensitive filesystems, two agents whose ids differ only by letter case would collide in storage, so make_baby_bot returns success: false with an error naming the conflicting id when that happens.

Creating an agent requires manage_agents or create_agents. A caller with only create_agents receives management rights on the agent it creates or imports, but not on other agents. Operations that change an existing agent require global manage_agents or a manage grant on that specific agent. Administrators can restore a missing creator grant through the RBAC API; see RBAC in Genesis.

Context-default validation is fail-fast. When make_baby_bot receives context-default settings, Genesis validates the capability policy and the default tool-group cap before writing the new agent. An invalid patch returns success: false with an error and structured details; no agent row is created, so you can correct the defaults and retry with the same bot_id. If validation passes but the later persistence step fails, the response identifies that the agent was created and includes a repair hint to use set_bot_context_defaults, assign_bot_role, and set_bot_knowledge_bases instead of creating it again.

`get_available_tools`

Parameters

Name	Definition	Format
include_functions	Include function details. Default `false`.	Boolean

`_remove_bot`

Parameters

Name	Definition	Format
bot_id	Id of the agent to delete.	String
confirmed	Must equal `!CONFIRM DELETE <bot_id>` to proceed with deletion.	String

Removing a data agent is permanent. Back up instructions and configs before calling _remove_bot.

`_list_all_bots`

Parameters

Name	Definition	Format
with_instructions	Include full instruction text. Default `false`.	Boolean

`_deploy_to_slack`

Parameters

Name	Definition	Format
bot_id	Agent id to deploy to Slack.	String
slack_app_token	Optional inline Slack master app token used for manifest operations.	String
slack_app_refresh_token	Inline Slack master refresh token used to obtain a fresh config token for deploy or redeploy.	String

Tool-driven Slack deployment requires inline master credentials. Provide slack_app_refresh_token on the deploy call, and optionally slack_app_token when you want Genesis to rotate from the current master token in the same step.

`add_new_tools_to_bot` (deprecated)

Deprecated. Use manage_context(action='ADD_CONTEXT', active_tool_groups='...') for per-thread activation, or set_bot_context_defaults(default_tool_groups=[...]) for durable defaults. This wrapper now redirects to the durable defaults path (it no longer writes the removed available_tools column).

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
new_tools	Tool group names to add to the durable defaults.	Array of strings

`remove_tools_from_bot` (deprecated)

Deprecated. Use manage_context(action='REMOVE_CONTEXT', active_tool_groups='...') for per-thread changes, or set_bot_context_defaults(default_tool_groups=[...]) for durable defaults. This wrapper now redirects to the durable defaults path.

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
remove_tools	Tool group names to remove from the durable defaults.	Array of strings

`update_bot_instructions`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
new_instructions	Replacement instruction text.	String
bot_instructions	Legacy alias for `new_instructions` when older workflows still use it.	String
confirmed	Must equal `CONFIRMED` before Genesis applies the instruction change.	String

Genesis previews the current and proposed instructions first, then requires a follow-up call with confirmed="CONFIRMED" before saving the update.

`add_bot_files`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
new_file_ids	File IDs to attach to the bot.	Array of strings
new_file_names	Legacy alias for `new_file_ids` when `new_file_ids` is not supplied.	Array of strings

File attachments are supported for OpenAI-based bots. Cortex-based bots return an error because that runtime does not support files.

`update_app_level_key`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
slack_app_level_key	New Slack app level key.	String

`_update_bot_implementation`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
bot_implementation	New runtime engine: `openai`, `azureopenai`, `cortex`, `databricks`, or `litellm` (LiteLLM sub-providers normalize to `litellm`).	String

`get_bot_knowledge_bases`

Parameters

Name	Definition	Format
bot_id	Target agent id whose current knowledge bases should be inspected.	String

Returns the assigned knowledge_base_ids, raw assignment rows, effective_knowledge_bases, and whether runtime search_knowledge_bases and read_knowledge_base_doc currently have any enabled knowledge bases to search or read for that bot.

`set_bot_knowledge_bases`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
knowledge_bases	Replacement set of registered knowledge-base IDs. Accepts a list, JSON array string, or comma-separated string.	String or Array of strings

Pass knowledge_base_id values, not raw document index names. If you need to create the reusable bundle first, use Knowledge Base Admin Tools.

`get_bot_context_defaults`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String

Returns success, bot_id, and a compact defaults object with thread-start tool groups and skills plus tool_access_mode, tool_access_list, skill_access_mode, and skill_access_list. Requires manage_agents.

`set_bot_context_defaults`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String
default_tool_groups	Tool groups to auto-load at thread start.	String, array of strings, or comma-separated string
default_skills	Skills to auto-load at thread start.	String, array of strings, or comma-separated string
never_compress_skills	Default skills whose injected text thread compression keeps in full. Pass the complete list; `[]` clears it.	String, array of strings, or comma-separated string
tool_access_mode	Tool-policy mode: `all`, `allowlist`, or `denylist`.	String
tool_access_list	Tool groups referenced by `tool_access_mode`.	String, array of strings, or comma-separated string
skill_access_mode	Skill-policy mode: `all`, `allowlist`, or `denylist`.	String
skill_access_list	Skills referenced by `skill_access_mode`.	String, array of strings, or comma-separated string

Supply at least one field to update. On success, returns success, bot_id, and the updated defaults snapshot. Requires manage_agents. Each never_compress_skills entry must also be in default_skills; exceeding the configured per-agent cap is rejected. See Advanced Settings for the cap and Agents Center and Skills for how never-compress affects injected skill text. When Genesis rejects the patch because of capability policy, thread preflight, or default auto-load caps, the tool returns success: false, a human-readable error string, and a structured details object (for example rejected_skills, skill_access_mode, skill_access_list, violation, and cap) so agents can adjust the request without guessing. Other failures return only success and error with no details key. Persistent defaults can retain a policy-authorized channel-bound group while its runtime adapter is temporarily unavailable; runtime availability is enforced when the group is activated for a thread. set_bot_capability_policy is a convenience wrapper that forwards only the policy fields to set_bot_context_defaults and shares the same error envelope.

`get_bot_capability_policy`

Parameters

Name	Definition	Format
bot_id	Target agent id.	String

Returns success, bot_id, and a policy object with tool_access_mode, tool_access_list, skill_access_mode, and skill_access_list. Requires manage_agents.

`agent_management`

Author and synchronize portable, Git-backed agent definitions. Requires manage_agents and manage_repos. Call EXPORT_PREVIEW before EXPORT_COMMIT whenever a user asks to make a local agent reusable across Genesis instances. Neither export nor sync applies agent lifecycle changes on any instance — per-instance enablement and applying a commit-pinned preview remain separate administrator actions in Config → Managed Sources.

Parameter	Type	Default	Notes
`action`	string	none	One of `REGISTER_MANAGED_SOURCE`, `SYNC_FROM_REPO`, `PUSH_TO_REPO`, `EXPORT_PREVIEW`, `EXPORT_COMMIT`.
`params`	object or JSON string	`{}`	Action-specific fields (see table below).

Action	`params` fields
`REGISTER_MANAGED_SOURCE`	`repo_id` (required). Optional: `source_id`, `remote_url`, `connection`, `release_ref`, `agents_root`, `enabled` (boolean). Registers the repository with `scan_types_enabled: ["agents"]`. Sync only previews agent changes; it does not apply them.
`SYNC_FROM_REPO`	`source_id` or `repo_id` (one required). Discovers agent changes from Git and returns a preview. Never applies agent lifecycle changes (`apply_agent_changes` is always `false`).
`EXPORT_PREVIEW`	`agent_id` (required; `bot_id` accepted as alias). Returns the strict, secret-free portable definition that would be written to `agent.yaml`.
`EXPORT_COMMIT`	`agent_id` (required). Optional: `source_id` or `repo_id`, `artifact_path`, `title`, `body`, `commit_message`. Writes `agents/<agent_id>/agent.yaml` to an isolated per-user worktree and opens a PR/MR. Does not enable or apply the agent on any instance.
`PUSH_TO_REPO`	`agent_id` (required). Optional: `title`, `body`, `commit_message`. Opens a PR/MR for valid edits already made in the managed agent workspace.

The exported agent.yaml manifest includes behavior and capability defaults only. It intentionally excludes Slack or Teams credentials, OAuth secrets, API keys, database credentials, attached files, knowledge bases, RBAC role assignments, and instance-specific deployment settings. For later edits to an already-managed definition, edit through the managed artifact workspace with

file(action="write"/"search_replace"/etc, repo_id="...", artifact_type="agent", artifact_id="&lt;agent_id&gt;", file_path="agent.yaml")

, then call PUSH_TO_REPO. For assigning catalog skills to bots, use Skill Admin Tools. For generic clone/branch Git work outside managed artifacts, use git_action. Example

agent_management(
    action="EXPORT_PREVIEW",
    params={"agent_id": "Analyst-k7m2x9"},
)

agent_management(
    action="EXPORT_COMMIT",
    params={
        "agent_id": "Analyst-k7m2x9",
        "source_id": "org-agent-definitions",
        "title": "Add Analyst agent definition",
        "commit_message": "Add agent 'Analyst-k7m2x9' to managed repo",
    },
)

`_modify_slack_allow_list`

Parameters

Name	Definition	Format
action	One of `LIST`, `GRANT`, `REVOKE`, `GRANT ALL`, `REVOKE ALL`.	String
bot_id	Target agent id.	String
user_identifier	Slack user id beginning with `U` (when applicable).	String
user_name	Full name for user lookup (optional).	String

Use Cases below are NOT limited to those and are only referenced as an example.

High-impact allow-list changes use confirmed action strings instead of a separate boolean flag. When Genesis returns a confirmation prompt, retry with the exact action it requests, such as GRANT CONFIRMED, GRANT ALL CONFIRMED, or REVOKE ALL CONFIRMED.

Use Cases

Data Engineering Agents
Build and operate data pipelines with guardrails. Grant data_connector_tools, dbt_action, and git_and_file_tools for model runs, schema checks, and versioned SQL changes. Example: An agent compiles and runs selected dbt models on demand, posts run results, and opens a PR with updated snapshots.
Data Ops Agents
Monitor jobs, surface incidents, and automate remediation steps. Combine genesis_job_tools, harvester_tools, jira_connector_tools, and slack_tools for alerting and ticketing. Example: On failed harvest or long-running warehouse jobs, the agent creates a Jira issue, posts context to Slack, and links logs.
Business Analyst Agents
Provide safe self-service analysis with read-only access. Use data_connector_tools for parameterized queries and export to Sheets via google_drive_tools. Example: An analyst asks for weekly revenue by segment; the agent runs a vetted query, returns a table, and publishes a refreshed Google Sheet.

Workflow/How It Works

Create a agent with a unique bot_id, instructions, implementation, and initial tools.
Grant or remove tools and assigned knowledge bases as the scope sharpens.
Deploy to Slack if collaboration is required.
Control access with allow lists or open access.
Iterate on instructions or switch implementations as needs evolve.
Retire safely when the data agent is no longer needed.

Integration Relevance

slack_tools for deployment and notifications.
project_manager_tools to align agents with missions and tasks.
data_connector_tools for data access in analytics and BI agents.
jira_connector_tools to create or update tickets from a agent.
file_manager_tools to capture outputs and attach artifacts.

Configuration Details

bot_id must match name-xxxxxx where xxxxxx is 6 letters or digits, and must be unique with case-sensitive equality across all agents.
Tool names must match get_available_tools exactly.
Choose the implementation based on model capability, latency, and cost.
Slack permissions should follow your org policy for user access and scopes.

Limitations or Notes

Deleting a data agent cannot be undone.
Tool grants are validated and will fail for unknown tools.
Slack deployment requires correct app configuration and workspace permissions.
Switching implementations can change model behavior and token limits.
Access control changes apply immediately and may interrupt active users.
Network connectivity is required for external integrations.

Output

Creation and updates
Agent id, configuration summary, granted tools, and deployment status.
Listings Arrays of data agents with ids, names, status, and optional instructions.
Access control Current allow list entries and confirmations for grants or revokes.
Deployment Slack integration status and any required follow ups.
Errors Clear messages for invalid ids, case-only bot_id collisions, missing permissions, or unsupported tools.

​Overview

​Tool Name

​Purpose

​Key Features & Functions

​Input Parameters for Each Function

​make_baby_bot

​get_available_tools

​_remove_bot

​_list_all_bots

​_deploy_to_slack

​add_new_tools_to_bot (deprecated)

​remove_tools_from_bot (deprecated)

​update_bot_instructions

​add_bot_files

​update_app_level_key

​_update_bot_implementation

​get_bot_knowledge_bases

​set_bot_knowledge_bases

​get_bot_context_defaults

​set_bot_context_defaults

​get_bot_capability_policy

​agent_management

​_modify_slack_allow_list

​Use Cases

​Workflow/How It Works

​Integration Relevance

​Configuration Details

​Limitations or Notes

​Output

Overview

Tool Name

Purpose

Key Features & Functions

Input Parameters for Each Function

`make_baby_bot`

`get_available_tools`

`_remove_bot`

`_list_all_bots`

`_deploy_to_slack`

`add_new_tools_to_bot` (deprecated)

`remove_tools_from_bot` (deprecated)

`update_bot_instructions`

`add_bot_files`

`update_app_level_key`

`_update_bot_implementation`

`get_bot_knowledge_bases`

`set_bot_knowledge_bases`

`get_bot_context_defaults`

`set_bot_context_defaults`

`get_bot_capability_policy`

`agent_management`

`_modify_slack_allow_list`

Use Cases

Workflow/How It Works

Integration Relevance

Configuration Details

Limitations or Notes

Output