execute_v2_application_schedule

Reads an immutable schedule version and publication state, or saves, publishes or deactivates an authorized schedule. Supply a stable key for writes and omit it for reads. A schedule pins the published target, recurrence, bindings and delegation.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

{
  "workspace_id": "{{workspace_id}}",
  "application_id": "operating-cube",
  "program": {
    "languageVersion": 2,
    "function": "schedule.version.read",
    "arguments": {
      "scheduleId": "{{schedule_id}}",
      "version": 1
    }
  }
}

{
  "properties": {
    "workspace_id": {
      "title": "Workspace Id",
      "type": "string"
    },
    "application_id": {
      "title": "Application Id",
      "type": "string"
    },
    "program": {
      "additionalProperties": true,
      "title": "Program",
      "type": "object"
    },
    "idempotency_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Idempotency Key"
    }
  },
  "required": [
    "workspace_id",
    "application_id",
    "program"
  ],
  "title": "execute_v2_application_scheduleArguments",
  "type": "object"
}

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines · Related workflow · Application-language function catalog