Tool Catalog

For creating your own toolkits, see Custom Tools.

Quick Start

The compile-safe path is BuiltInTool — pass enum constants and the framework instantiates the backing POJO for you:

import com.tnsai.agents.AgentBuilder;
import com.tnsai.enums.BuiltInTool;
import com.tnsai.llm.providers.OpenAIClient;

Agent agent = AgentBuilder.create()
    .llm(new OpenAIClient("gpt-4o"))
    .role(myRole)
    .builtInTools(
        BuiltInTool.WEB_SEARCH_TOOLS,   // brave_search, duckduckgo, wikipedia, …
        BuiltInTool.UTILITY_TOOLS,      // calculator, hash, datetime_*
        BuiltInTool.PDF_TOOLS           // pdf_extract_text, pdf_metadata, …
    )
    .build();

String response = agent.chat("What is the population of Tokyo? Triple it.");

The LLM sees every @Tool method on every registered toolkit as a callable function and dispatches by method name (brave_search, calculator, pdf_extract_text, …). Most toolkits read credentials from environment variables on first use:

export BRAVE_API_KEY=your-key
export OPENAI_API_KEY=your-key

How toolkits are organised

Each BuiltInTool enum entry maps a stable toolName to the FQCN of a POJO in tnsai-tools. The POJO's public @Tool-annotated methods are the actual functions exposed to the LLM. For example, BuiltInTool.CSV_TOOLS backs com.tnsai.tools.file.CsvTools, which exposes csv_summary, csv_columns, csv_filter, csv_head, csv_search.

Tables below list each toolkit's enum constant, backing class, the methods it exposes, and any required environment variables. Method names are what the LLM will see and call.

search

Web search, scraping, and specialised lookups.

academic

Free / freemium scholarly databases.

file

Text and structured-document parsing.

CSV_TOOLS — example

CsvTools is the canonical example for the function-shape pattern. The five methods below are independent — the LLM picks the one it needs.

Agent agent = AgentBuilder.create()
    .llm(new OpenAIClient("gpt-4o"))
    .role(myRole)
    .builtInTools(BuiltInTool.CSV_TOOLS)
    .build();

agent.chat("Summarise /data/sales.csv and list the column headers.");
// LLM emits two tool calls: csv_summary("/data/sales.csv") then csv_columns(...)

The methods accept typed parameters (path, column name, etc.) — there's no path|||command text protocol any more. Each method is a regular Java method whose signature defines the LLM-facing schema (via @Tool and @ToolParam).

communication

Email, chat, and SMS sending.

fintech

Payment and BNPL platforms.

commerce

Storefront APIs.

crm

Customer-relationship platforms.

database

Relational, document, key-value, and vector stores.

developer

Repo, dependency, and project introspection.

productivity

Calendars, task trackers, docs.

media

Audio and TTS.

social

Social-network APIs.

ai

Multimodal helpers.

code

Code execution through the framework's Sandbox SPI. Both built-in tools route through SandboxFactory.byId("process") by default with ResourceLimits.standard() + NetPolicy.denyAll(). Pass an explicit SandboxFactory + image-bearing SandboxSpec via the full-control constructors for container / WASM / Firecracker isolation.

utility

Math, hashing, datetime, encoding.

diagram

Diagram-as-code rendering.

document

DOCX / Office / image conversion.

visualization

Charts, tables, infographics.

realtime

Live FX, crypto, weather feeds.

finance

Borsa Istanbul market data.

trading

Prediction markets.

scraping

Apify actor execution.

knowledge

In-memory knowledge graph.

memory

Persistent recall.

goose

Desktop automation.

project

Repo-level read helpers.

agentsmd_parse returns an AgentsMdContent record (intro + ordered sections: [{level, title, body}]) parsed from AGENTS.md, with case-variant + CLAUDE.md + README.md fallback. Use this when an agent needs to route on individual sections (e.g. pull the "Setup" body) rather than the whole document. agentsmd_generate produces a draft AGENTS.md by detecting the build system from pom.xml / package.json / pyproject.toml / Cargo.toml / go.mod and filling in language-appropriate setup + test commands — returns the markdown string, the caller decides whether to write it.

system

HTTP and tool discovery.

Direct instantiation

If you need to register a toolkit outside the AgentBuilder.builtInTools(...) path — for example, from a plugin loader — every entry has a no-arg instantiate() method that returns a fresh POJO ready for ToolMethodRegistry:

Object csvToolkit = BuiltInTool.CSV_TOOLS.instantiate();
// csvToolkit is a com.tnsai.tools.file.CsvTools instance

instantiate() throws BuiltInToolInstantiationException if tnsai-tools is missing from the classpath (the FQCN string isn't resolvable) or if the POJO's public no-arg constructor fails.

Authoritative source

The full per-toolkit Javadoc — including every @Tool method's exact signature and the corresponding @ToolParam constraints — lives in com.tnsai.enums.BuiltInTool and the backing POJOs under com.tnsai.tools.*.