Fix McpListTask input schema to require server or transport configuration

[Copilot]

McpListTask's inputSchema only required list_type, making inputs with no server/transport configuration schema-valid while always failing at runtime when the MCP client is created.

Changes

• allOf extended with anyOf: [{ required: ["server"] }, { required: ["transport"] }] — schema now rejects inputs that provide neither a registry server ID nor an inline transport
• Top-level if/then/else — conditionally requires command for stdio transport, server_url for all other transports

required: ["list_type"],
if: { properties: { transport: { const: "stdio" } }, required: ["transport"] },
then: { required: ["command"] },
else: {
  if: { required: ["transport"] },
  then: { required: ["server_url"] },
},
allOf: [
  ...mcpServerConfigSchema.allOf,
  { anyOf: [{ required: ["server"] }, { required: ["transport"] }] },
],

This aligns McpListTask's input schema with the conditional validation pattern already present in the config schemas of McpToolCallTask, McpPromptGetTask, and McpResourceReadTask.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.