MCP schedule tools missing timeout_seconds, allowed_tools, and model parameters

[vybe]

Bug Description

The MCP server's create_agent_schedule and update_agent_schedule tools are missing several parameters that the backend API fully supports. Users cannot set timeout_seconds, allowed_tools, or model when creating or updating schedules via MCP.

Root Cause

The Zod schemas in the MCP tool definitions and the TypeScript interfaces in types.ts do not include these fields, even though the backend models (ScheduleCreate, ScheduleUpdate, ScheduleResponse) support them.

Affected Files

• src/mcp-server/src/tools/schedules.ts — tool parameter schemas missing fields
• src/mcp-server/src/types.ts — Schedule, ScheduleCreate, ScheduleUpdate interfaces missing fields

What's Missing

Parameter	Backend Support	MCP Tool Support
timeout_seconds	✅ (default 900)	❌
allowed_tools	✅	❌
model	✅	❌

Impact

• Users cannot set custom execution timeouts for schedules via MCP (stuck with default 15 min)
• Users cannot restrict which tools a scheduled execution can use via MCP
• Users cannot override the model per schedule via MCP
• Workaround: Use the REST API directly instead of MCP

Expected Fix

1. Add timeout_seconds, allowed_tools, and model to the Zod schemas in create_agent_schedule and update_agent_schedule tool definitions
2. Add the same fields to the TypeScript interfaces in types.ts
3. Rebuild the MCP server

[vybe]

Fixed. Added timeout_seconds, allowed_tools, and model parameters to MCP schedule tool Zod schemas, TypeScript interfaces, and pass-through logic in both create_agent_schedule and update_agent_schedule tools.