tool_use API, the Vercel AI SDK, and any other provider that accepts JSON Schema tool descriptions. CL SDK gives you the definitions — the typed input schemas and descriptions — and you implement the execution logic. This separation means the agent can be provider-agnostic while your business logic stays in your own codebase.
Available Tools
DOCUMENT_LOOKUP_TOOL
Search and retrieve insurance documents by ID, policy number, carrier, or free-text query. The agent calls this tool when a user refers to a policy or quote without specifying an exact document ID.COI_GENERATION_TOOL
Request generation of a Certificate of Insurance for a specific policy. The agent calls this when a user asks for a COI andcoiHandling is set to permit self-service generation.
COVERAGE_COMPARISON_TOOL
Compare coverages across two or more insurance documents. The agent calls this when a user asks to compare quotes, check renewal differences, or evaluate competing options.ToolDefinition Type
All exported tool constants satisfy theToolDefinition interface:
tools array directly.
Using All Tools Together
AGENT_TOOLS is a convenience export that bundles all three tool definitions into a single array. Use it with buildAgentSystemPrompt for a complete agent setup.
CL SDK does not execute tool calls. Your application is responsible for implementing the handler for each tool name and returning the tool result back to the LLM in the next message turn.
Selective Tool Registration
You can register a subset of tools if your agent doesn’t support all operations. For example, an agent that handles read-only queries should omitCOI_GENERATION_TOOL:
Adding Custom Tools
To add your own tools alongside the CL SDK definitions, define them using the sameToolDefinition shape and merge the arrays: