Tools Basics

DocsGPT Tools are powerful extensions that significantly enhance the capabilities of your DocsGPT application. They allow DocsGPT to move beyond its core function of retrieving information from your documents and enable it to perform actions, interact with external data sources, and integrate with other services. You can find and configure available tools within the “Tools” section of the DocsGPT application settings in the user interface.

What are Tools?

• Purpose: The primary purpose of Tools is to bridge the gap between understanding a user’s request (natural language processing by the LLM) and executing a tangible action. This could involve fetching live data from the web, sending notifications, running code snippets, querying databases, or interacting with third-party APIs.

• LLM as an Orchestrator: The Large Language Model (LLM) at the heart of DocsGPT is designed to act as an intelligent orchestrator. Based on your query and the declared capabilities of the available tools (defined in their metadata), the LLM decides if a tool is needed, which tool to use, and what parameters to pass to it.

• Action-Oriented Interactions: Tools enable more dynamic and action-oriented interactions. For example:

  • “What’s the latest news on renewable energy?” - This might trigger a web search tool to fetch current articles.
  • “Fetch the order status for customer ID 12345 from our database.” - This could use a database tool.
  • “Summarize the content of this webpage and send the summary to the #general channel on Telegram.” - This might involve a web scraping tool followed by a Telegram notification tool.

Overview of Built-in Tools

DocsGPT includes a suite of pre-built tools designed to expand its capabilities out-of-the-box. Below is an overview of the currently available tools.

API Tool

A highly flexible tool that allows DocsGPT to interact with virtually any API without needing to write custom Python code.

Brave Search

Enables DocsGPT to perform real-time web and image searches using the Brave Search API. Requires an API key.

DuckDuckGo Search

Performs web and image searches using DuckDuckGo. No API key required.

CryptoPrice

Fetches the current price of specified cryptocurrencies using the CryptoCompare public API.

Ntfy

Allows DocsGPT to send push notifications to ntfy topics on a specified server, ideal for alerts and updates.

Telegram Bot

Allows DocsGPT to send messages or images to Telegram chats via a Telegram Bot. Requires a bot token; an optional default chat ID sends every message to one chat.

PostgreSQL Database

Connects to a PostgreSQL database to execute SQL queries and retrieve schema information.

Read Webpage (browser)

Fetches the HTML content of a URL and converts it to Markdown for the agent to read.

Remote Device

Runs shell commands on a paired remote machine through the docsgpt-cli host. See the Remote Device guide.

MCP Tool

Connects to remote Model Context Protocol (MCP) servers to access their dynamic tools and resources.

Memory

Stores and retrieves information across conversations through a per-user memory file directory.

Notepad

A single editable note. Supports viewing, overwriting, string replacement, inserting lines and deleting the note.

Todo List

Manages todo items — creating, viewing, updating, and deleting todos.

Code Executor

Runs Python in a sandboxed session and saves the files it writes as downloadable artifacts. Needs a code execution sandbox.

Artifact

Creates and edits slide decks, Word documents, spreadsheets, PDFs and HTML pages as versioned artifacts. Needs a code execution sandbox.

Code Executor and Artifact run code in a sandbox that you set up first; see Code Execution Sandbox.

Some built-in tools aren’t in the catalog because DocsGPT attaches them itself:

• Scheduler lets the assistant schedule a task to run later. It is one of the default chat tools below, and you can also enable it per agent in the agent’s tool picker. Scheduled and webhook runs never get it.
• Read Document parses an uploaded or produced file into text or structured data. It is offered only in workflow nodes; see Artifacts and Code Execution.
• Wiki reads and edits a wiki source. It is attached automatically to a chat or agent that uses a wiki source you can edit; see Wiki Sources.

Default Chat Tools

In a regular chat (no custom agent), DocsGPT can enable a small set of tools automatically so the assistant is useful out of the box. These are the default chat tools, controlled by the DEFAULT_CHAT_TOOLS setting:

DEFAULT_CHAT_TOOLS=["memory","read_webpage","scheduler"]

• Default tools are config-free and run with synthetic, deterministic tool IDs (no manual setup needed).
• Each user can opt out of individual default tools from their settings; the disabled list is stored per user.
• Some default tools are excluded from headless runs (scheduled tasks and webhook triggers). For example, scheduler is skipped in those runs to prevent a scheduled task from chaining new schedules on every fire.

To change the defaults for the whole instance, set DEFAULT_CHAT_TOOLS to a JSON list of tool names, as above. Comma-separated names (memory,read_webpage) are accepted too. To turn the default tools off, set DEFAULT_CHAT_TOOLS=none (or []); an empty value keeps the shipped defaults. See the Settings Reference for the full entry.

The Tools page

Settings → Tools shows your tools as cards, grouped the same way as the tool pickers:

• Included: tools that come with DocsGPT, such as the default chat tools. The agent builder’s picker also lists Code Executor and Artifact here.
• Added: tools you added from the catalog with Add tool and configured.
• One group per connected service, headed by the service’s icon and name. Each card names the account it uses. These tools are managed in Settings → Connectors.
• Custom: API tools and MCP servers you made.

A card’s last line holds its facts: the account it uses, your role on a tool a team shared with you, and N agents, which you can click for a list of links to the agents that use it. The switch at the card’s bottom right turns the tool on or off in your chats without an agent; hover it to see which.

To narrow the page, All, Included, Added, Services and Custom filter by group, each with its count of the tools your search matches, and the Any use menu beside them shows only the tools that are In use (by an agent or your chats) or Unused. The menu appears only when it would narrow the list, so not while every tool is in use. Deleting a tool that agents use says how many lose it.

In a chat, the composer’s Tools menu uses the same groups, and so does the agent builder’s Tools field (Select tools) and a workflow’s agent node. They list the tools already selected first, under Selected, and end with Go to Tools, which opens this page, and Add tool. A tool you add from an agent’s picker, or a workflow node’s, is selected there once it is set up. In the agent and workflow builders, Go to Tools and the links that leave from Add tool ask first when you have unsaved changes. When you have more than 10 tools, the same group filter appears under the search.

Using Tools in DocsGPT (User Perspective)

Interacting with tools in DocsGPT is designed to be intuitive:

1. Natural Language Interaction: As a user, you typically interact with DocsGPT using natural language queries or commands. The LLM within DocsGPT analyzes your input to determine if a specific task can or should be handled by one of the available and configured tools.

2. Configuration in UI:

   • Tools are generally managed and configured within the DocsGPT application’s settings, found under a “Tools” section in the GUI.
   • Tools for external services (Brave Search, Telegram, ntfy, PostgreSQL, MCP servers, GitHub, and preset MCP services for Notion, Linear, Jira & Confluence, Sentry, Stripe, Resend and Cloudflare) are set up from Settings > Connectors. You connect the service once; its credentials stay encrypted on the server and never reach the browser, and the tools it provides are grouped under that service, with the account on each tool. Each action is marked Read or Write and can be set to Always allow, Needs approval or Off. See Connectors.
   • When a tool’s connection is missing or expired, the chat shows a Connect prompt and continues once you connect.

3. Prompt Engineering for Tools: While the LLM aims to intelligently use tools, for more complex or reliable agent-like behaviors, you might need to customize the system prompts. Modifying the prompt can guide the LLM on when and how to prioritize or chain tools to achieve specific outcomes, especially if you’re building an agent designed to perform a certain sequence of actions every time. For more on this, see Prompts.

Advancing with Tools

Understanding the basics of DocsGPT Tools opens up many possibilities:

• Leverage the API Tool: For quick integrations with numerous external services, explore the API Tool Detailed Guide.
• Develop Custom Tools: If you have specific needs not covered by built-in tools or the generic API tool, you can develop your own. See Developing Custom Tools.
• Build AI Agents: Tools are the fundamental building blocks for creating sophisticated AI agents within DocsGPT. See Agents Basics for how to combine them in an agent.

By harnessing the power of Tools, you can transform DocsGPT into a more versatile and proactive assistant tailored to your unique workflows.