Added Strategy 2.5 to schema extraction to handle AI SDK v6's jsonSchema() wrapper which uses `.jsonSchema` property instead of `.schema`. This fixes schema validation errors for @tpmjs/hello and other packages that use jsonSchema() wrapper. Error was: "No valid schema found" with keys ["_type", "jsonSchema", "validate"] Fix: Check for inputSchema.jsonSchema as an object property 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| deno.json | ||
| Dockerfile | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| server.js | ||
| server.ts | ||
Railway Dynamic Tool Executor
Dynamic tool executor service that runs with --experimental-network-imports to support loading npm packages from esm.sh at runtime.
Features
- 🔥 Dynamic imports from esm.sh
- 💾 Module caching for fast repeated loads
- 🛡️ Validation of AI SDK tool structure
- 🚀 Remote execution of tools with parameters
Endpoints
GET /health
Health check and cache statistics
POST /load-and-describe
Load a tool from esm.sh and return its schema
Request:
{
"packageName": "firecrawl-aisdk",
"exportName": "webSearchTool",
"version": "0.7.2",
"importUrl": "https://esm.sh/firecrawl-aisdk@0.7.2"
}
Response:
{
"success": true,
"tool": {
"exportName": "webSearchTool",
"description": "Search the web using Firecrawl",
"inputSchema": { ... }
}
}
POST /execute-tool
Execute a tool with parameters
Request:
{
"packageName": "firecrawl-aisdk",
"exportName": "webSearchTool",
"version": "0.7.2",
"params": {
"query": "latest AI news"
}
}
Response:
{
"success": true,
"output": { ... },
"executionTimeMs": 1234
}
POST /cache/clear
Clear the module cache
GET /cache/stats
Get cache statistics
Local Development
# Install dependencies
npm install
# Start server
npm start
# Server runs on http://localhost:3001
Railway Deployment
This service is designed to run on Railway.
Deploy Steps
- Initialize Railway in this directory:
cd apps/railway-executor
railway init
- Link to your Railway project:
railway link
- Deploy:
railway up
- Railway will automatically:
- Detect Node.js
- Run
npm install - Execute
npm start(which includes--experimental-network-imports)
Environment Variables
No environment variables required for basic operation. Optional:
PORT- Server port (Railway sets this automatically)NODE_ENV- Set toproductionin Railway
Testing
Test health endpoint:
curl http://localhost:3001/health
Test tool loading:
curl -X POST http://localhost:3001/load-and-describe \
-H "Content-Type: application/json" \
-d '{
"packageName": "@tpmjs/hello",
"exportName": "helloWorldTool",
"version": "0.1.0"
}'
Test tool execution:
curl -X POST http://localhost:3001/execute-tool \
-H "Content-Type: application/json" \
-d '{
"packageName": "@tpmjs/hello",
"exportName": "helloWorldTool",
"version": "0.1.0",
"params": {}
}'
Integration with Playground
The playground app calls this service to load and execute tools dynamically.
Set in playground environment:
RAILWAY_SERVICE_URL=https://your-service.up.railway.app
Or use existing:
SANDBOX_EXECUTOR_URL=https://your-service.up.railway.app