What problem does it solve?
Vovk.ts LLM tools empower developers to turn existing server code into LLM-consumable tools by deriving tools from Controllers, RPC modules, and OpenAPI mixins, or by creating standalone tools without controllers. This skill provides a unified workflow for building, formatting, and dispatching tools that work across HTTP and MCP backends.
Core Features & Use Cases
- Derive tools from Controllers, RPC modules, and OpenAPI mixins using deriveTools({ modules }). The resulting tools can be consumed by OpenAI/Anthropic function calling or MCP servers, and can be dispatched via toolsByName for in-process execution.
- Create standalone tools with createTool({ … }), including input/output schemas, execute handlers, and optional formatting via ToModelOutput, enabling non-controller code (calculators, SDK wrappers, file ops) to participate in the tool ecosystem.
- Configure per-tool metadata and control visibility via @operation.tool, hidden flags, and naming conventions to tailor LLM-facing surfaces while maintaining a single underlying execution path.
- Integrate with MCP by selecting ToModelOutput.MCP, enabling multi-block, annotated content and optional per-call overrides for combined HTTP/LLM workflows.
- Use meta/context, withDefaults for auth-in-advance, and support for mixins, ensuring a cohesive tool surface across a Next.js project.
Quick Start
Expose your API surface to an LLM by configuring deriveTools or createTool and test function-calling integration.