feat(codeflows): defineTool Zod→OpenAPI custom tools primitive

[DumbMachine]

Summary

Custom tools are authored with @access/tools defineTool where Zod is the authoring primitive and OpenAPI is the wire. Deploy persists parameters + a mini OpenAPI 3 doc; MCP reuses the same discover / describe / execute surface agents already use for rest_api.

Authoring

import { defineTool, z } from "@access/tools";

export default defineTool({
  name: "twitter-search",
  description: "Search tweets",
  input: z.object({
    query: z.string().describe("Search query"),
  }),
  async invoke(input) { /* ... */ },
});

Agent / MCP contract

• discover(kind="tool") — lists deployed tools
• describe(kind="integration", slug="tool") — argv grammar
• describe(kind="resource", slug="<tool>") — OpenAPI ops (invoke)
• describe(..., query="invoke") — Zod→OpenAPI input_schema
• execute({ resource, argv: ["http","invoke"], stdin }) — same shape as rest_api
• Workflows: client.tool("name").invoke(input)

Implementation

• New sdk/tools (defineTool + Zod 4 toJSONSchema target openapi-3.0)
• Embedded runtime for esbuild (@access/tools virtual module)
• Deploy probes defineTool metadata; legacy export const tool still upgrades to OpenAPI
• MCP tools_custom.go + ToolBroker wired into mcpServer()
• Tool detail UI shows Parameters + OpenAPI
• Example tools migrated to defineTool

UI (prior)

• Resources Integrations|Tools segment; full-bleed tool detail Chrome

Screenshots

Tools list

Tools list

Tool detail

Tool detail

Tool source

Tool source

Workflow using tools

Workflow activity

Test plan

• go test ./core/codeflows/ ./core/mcpserver/
• defineTool deploy + invoke + workflow test (multi-instance)
• Legacy static export const tool still deploys
• Unsupported tool capability fails explicitly
• Re-bootstrap demo + refresh screenshots with OpenAPI panel

_{To show artifacts inline, enable in settings.}