AI Tools Browser

The AI Tools Browser provides a comprehensive view of all available MCP (Model Context Protocol) tools in your MoLOS instance. It's designed to help you understand what capabilities are available to AI assistants and how to effectively use them.

Overview

Location: /ai/tools (or navigate via AI → Tools)

The Tools Browser is an essential resource for:

• Discovering available tools - See all tools across all modules
• Understanding capabilities - Learn what each tool does
• Exploring parameters - Understand required and optional inputs
• Filtering by module - Focus on tools for specific areas
• Planning integrations - Identify tools for custom AI workflows

The AI Tools Browser showing tools filtered by the Tasks module

Accessing the Tools Browser

1. Click AI in the main navigation
2. Select Tools from the dropdown menu
3. The browser will load with all available tools displayed

Alternatively, use the quick navigation from the AI Dashboard.

Interface Components

Search Bar

At the top of the browser, a search bar allows you to quickly find tools:

• Real-time filtering as you type
• Searches tool names and descriptions
• Fuzzy matching for typo tolerance

Module Filters

On left side (or top on mobile), you'll find module filter buttons:

Filter	Description
All	Show tools from all modules
Tasks	Task, project, and area management tools
Markdown	Documentation and notes tools
LLM Council	Multi-agent AI discussion tools

Tool Cards

Each tool is displayed as a card containing:

• Tool Name - The unique identifier (e.g., molos_tasks_create_task)
• Module Badge - Which module the tool belongs to
• Description - What the tool does
• Parameters - Required and optional inputs
• Expand Button - Show full parameter details

Filtering by Module

Filtering helps you focus on tools relevant to a specific area:

How to Filter

1. Locate the module filter buttons
2. Click on a module name to filter
3. Only tools from that module will be displayed
4. Click All to show everything again

Module Tool Counts

Here's a typical distribution of tools per module:

Module	Tool Count	Primary Functions
Tasks	~30	CRUD operations, dependencies, comments
Markdown	~19	Pages, quick notes, versions
LLM Council	~10	Council management, personas

Tool Availability

Tool counts may vary based on your installed modules and version. The browser always shows the current available tools for your instance.

Searching Tools

Search Capabilities

The search function supports:

• Tool name matching - Find tools by their identifier
• Description search - Search within tool descriptions
• Partial matching - Find tools with partial keyword matches

Search Tips

Effective Searching

• Use action verbs: "create", "delete", "update", "get"
• Include module names: "task", "health", "meal"
• Be specific: "bulk create tasks" vs just "create"
• Try synonyms: "add" might find "create" tools

Example Searches

Search Query	Results
create	All tools that create items
task dependency	Tools for managing task dependencies
bulk	Tools that operate on multiple items
comment	Tools for creating/managing comments
markdown page	Tools for page management

Tool Descriptions

Each tool card displays a description explaining its purpose:

Description Format

[Tool Name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Module: Tasks

Creates a new task. Tasks must belong to a project. 
Supports setting title, description, priority, due date, 
and task type.

Required: title, projectId
Optional: description, priority, dueDate, taskType

Understanding Descriptions

Good tool descriptions include:

1. Primary action - What the tool does
2. Requirements - What's needed to use it
3. Options - What can be customized
4. Side effects - Any additional changes made

Tool Parameters

Parameters define the inputs a tool accepts. Understanding them is crucial for effective tool usage.

Parameter Types

Type	Description	Example
string	Text value	"Buy groceries"
number	Numeric value	42, 3.14
boolean	True/false	true, false
enum	Predefined options	"high", "medium", "low"
array	List of values	["tag1", "tag2"]
object	Nested structure	{"key": "value"}

Required vs Optional

Required parameters must be provided for the tool to work:

Required Parameters:
├── title (string)
│   └── The task title (1-200 characters)
└── projectId (string)
    └── ID of the parent project

Optional parameters enhance functionality but aren't mandatory:

Optional Parameters:
├── description (string)
│   └── Detailed task description
├── priority (enum)
│   └── Options: "urgent", "high", "medium", "low", "no_priority"
│   └── Default: "medium"
├── dueDate (number)
│   └── Unix timestamp in seconds
└── taskType (enum)
    └── Options: "task", "bug", "feature", "epic", "story"
    └── Default: "task"

Parameter Validation

MoLOS validates parameters before executing tools:

• Type checking - Values must match expected types
• Range limits - Numbers within valid ranges
• Enum validation - Only accepted values allowed
• Format requirements - Dates, IDs in correct format

Validation Behavior

If a tool receives invalid parameters:

1. The tool returns an error message
2. No changes are made to your data
3. The error explains what went wrong

Exploring Specific Tools

Let's look at some commonly used tools and their parameters:

Task Creation Tool

Tool: molos_MoLOS-Tasks_bulk_create_tasks

Purpose: Create multiple tasks at once

Parameters:

Name	Type	Required	Description
tasks	array	Yes	Array of task objects
tasks[].title	string	Yes	Task title
tasks[].projectId	string	Yes	Parent project ID
tasks[].description	string	No	Task description
tasks[].priority	enum	No	Priority level
tasks[].dueDate	number	No	Due date timestamp
tasks[].taskType	enum	No	Task type

Example Usage:

{
  "tasks": [
    {
      "title": "Review PR #42",
      "projectId": "proj_abc123",
      "priority": "high",
      "taskType": "task"
    },
    {
      "title": "Fix login bug",
      "projectId": "proj_abc123",
      "priority": "urgent",
      "taskType": "bug"
    }
  ]
}

Markdown Page Tool

Tool: molos_MoLOS-Markdown_create_markdown_page

Purpose: Create a new documentation page

Parameters:

Name	Type	Required	Description
title	string	Yes	Page title
content	string	No	Markdown content
path	string	No	Hierarchical path
tags	array	No	Tags for categorization

Using Tools with the Architect Agent

The Architect Agent automatically has access to all tools. When you chat with it:

1. Natural language understanding - Describe what you want in plain language
2. Automatic tool selection - The Architect picks the right tool
3. Parameter extraction - Details from your message fill parameters
4. Confirmation - You see what was done

Example Conversation Flow

You: "Create two high priority tasks in my Work project: 
     review the design mockups and update the API documentation"

Architect: [Internally]:
  1. Identifies tool: bulk_create_tasks
  2. Finds "Work" project ID
  3. Extracts task details
  4. Sets priority to "high"
  5. Executes tool

Architect: "Created 2 tasks in your Work project:
  • Review the design mockups (High priority)
  • Update the API documentation (High priority)"

Best Practices

Discovering Tools

Exploration Tips

• Browse by module when learning a new feature
• Use search when you know what you want to do
• Read descriptions to understand capabilities
• Check parameters to know what's required

Working with Parameters

• Required parameters must always be provided
• Optional parameters have sensible defaults
• Enums only accept specific values (invalid values use defaults)
• Arrays can often be empty for "get all" operations

Error Handling

When tools fail:

1. Read the error message - It usually explains the issue
2. Check required parameters - Missing something?
3. Validate types - String vs number mismatch?
4. Verify IDs - Does the referenced item exist?

Related Documentation

• AI Chat & The Architect - Using tools through conversation
• Integrating AI Clients - Connecting external AI tools
• Module Documentation - Learn about each module

---

Last Updated: March 22, 2026