Tool Catalog Reference
Quick lookup. Full documentation with per-toolkit method lists and usage examples: capabilities/tools/catalog.
TnsAI ships 62 POJO toolkits exposing roughly 206 @Tool-annotated methods across 29 categories. Each toolkit is a plain class in tnsai-tools with public @Tool methods that the framework discovers reflectively at agent build time.
Categories
academic, ai, code, commerce, communication, crm, database, developer, diagram, document, file, finance, fintech, goose, knowledge, media, memory, productivity, project, realtime, scraping, search, social, system, trading, utility, visualization.
Finding a toolkit
The compile-safe path is the BuiltInTool enum — every entry maps a stable toolName to the FQCN of a backing POJO:
import com.tnsai.enums.BuiltInTool;
// Register on an agent
Agent agent = AgentBuilder.create()
.llm(llm)
.role(role)
.builtInTools(BuiltInTool.WEB_SEARCH_TOOLS, BuiltInTool.PDF_TOOLS)
.build();
// Or instantiate directly
Object pdfToolkit = BuiltInTool.PDF_TOOLS.instantiate();
// Inspect catalog
for (var entry : BuiltInTool.values()) {
System.out.println(entry.getToolName() + " — " + entry.getClassName());
}Inspecting registered tools at runtime
Each agent has a ToolMethodDispatcher whose registry() exposes every @Tool method registered with that agent:
import com.tnsai.tools.method.ToolMethodRegistry;
ToolMethodRegistry registry = agent.getToolMethodDispatcher().registry();
for (var tool : registry.allMethods()) {
System.out.println(tool.name() + " — " + tool.description());
}For the complete list with per-toolkit method names, parameter shapes, and required environment variables, see capabilities/tools/catalog.
Semantic Annotation Framework
Previous Page
SPI Reference
TnsAI.Core uses Java's ServiceLoader mechanism extensively for cross-module extensibility. SPI interfaces define contracts in the core module; implementations live in optional modules and are discovered at runtime via META-INF/services/ registration.