get-schedule
Read one schedule by its schedule_id. Needs the fabric:orchestrate.read grant.
curl -sS -X POST https://fabric.wexa.ai/mcp/$FABRIC_PROJECT_ID \
-H "authorization: Bearer $FABRIC_API_KEY" \
-H "Mcp-Session-Id: $MCP_SESSION_ID" \
-H "content-type: application/json" -H "accept: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get-schedule","arguments":{"schedule_id":"6ab194677566f41b5c28e30f"}}}'{
"content": [
{
"type": "text",
"text": "{\"lifecycle_id\":\"qlc_000188\",\"result\":{\"schedule_id\":\"6ab194677566f41b5c28e30f\",\"agentflow_id\":\"6ab1945e7566f41b5c28e303\",\"goal\":\"Summarise yesterday's orders.\",\"frequency\":\"0 9 * * 1\",\"time_zone\":\"Asia/Kolkata\",\"type\":\"recurring\",\"status\":\"active\",\"run_count\":0}}"
}
],
"isError": false
}Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
schedule_id | string | Required | Schedule id from list-schedules or create-schedule. A schedule in this project. |
Show full response
A real response, captured from a live call to get-schedule:
{
"lifecycle_id": "qlc_000188",
"result": {
"agentflow_id": "6ab1945e7566f41b5c28e303",
"conclusion": null,
"created_at": 1790022759.401271,
"created_by": "6a79a770b6c128ccc24bfca7",
"end_at": null,
"frequency": "0 9 * * 1",
"goal": "Summarise yesterday's orders.",
"last_execution_id": null,
"limit": null,
"run_at": null,
"run_count": 0,
"schedule_id": "6ab194677566f41b5c28e30f",
"status": "active",
"time_zone": "Asia/Kolkata",
"type": "recurring",
"updated_at": null
}
}More details
It returns the agent or process flow the schedule runs, its goal, its cron expression or single instant, its status, how many times it has run and last_execution_id, which get-execution takes unchanged.
Not marked consequential: it is audited lightly and the project's write gate never holds it.
Every tool call works the same way: How every tool call works.