feat(component-sdk): add tool mode metadata for agent-callable components

[betterclever]

Summary

Adds metadata types and helper functions for agent-callable components (tool mode). This enables components to be used as tools by AI agents via the MCP gateway.

Changes

Types (`types.ts`)

• Added `PortBindingType`: `'credential' | 'action' | 'config'`
• Added `bindingType` field to `ComponentPortMetadata`
• Added `AgentToolConfig` interface with `enabled`, `toolName`, `toolDescription`
• Added `agentTool` field to `ComponentUiMetadata`

Helper Functions (`tool-helpers.ts`)

• `isAgentCallable(component)` - Check if component is agent-callable
• `inferBindingType(port)` - Infer binding type from port data type
• `getCredentialInputIds(component)` - Get IDs of credential inputs
• `getActionInputIds(component)` - Get IDs of action inputs
• `getToolSchema(component)` - Get JSON Schema for action inputs only
• `getToolName(component)` - Get tool name for MCP
• `getToolDescription(component)` - Get tool description
• `getToolMetadata(component)` - Get complete MCP tool metadata

Tests

• 14 tests covering all helper functions

Linear Issue

Closes ENG-95

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e4d294d12

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Do not force json/any ports to object in tool schema

portTypeToJsonSchemaType maps both json and any to the JSON Schema type object, but coercePrimitive in ports.ts accepts any value for these port types (strings, numbers, arrays, etc.). This makes the generated MCP inputSchema reject legitimate non-object inputs (e.g., a JSON array or string) or mislead agents about the expected shape. Consider omitting type for these ports or using a permissive schema so tool calls that pass valid non-object JSON aren’t rejected.

Useful? React with 👍 / 👎.