taskGet
Retrieve specific task details from Routine by providing a unique task ID. Simplify task management and tracking with direct access to task information.
Instructions
A task.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Implementation Reference
- src/tools.ts:806-832 (registration)Registration of the taskGet tool including inline Zod schema for input 'id' (string) and the handler function that sends an RPC request to 'task.get' with the id and returns the JSON-formatted response or an error.
"taskGet", "A task.", { /* {"$id":"#task-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"} */ id: z.string(), }, async ({ id }) => { try { const data = await sendRpcRequest("task.get", [id]); return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }], }; } catch (error) { logger.error("Error fetching task.get: %o", error); return { content: [ { type: "text", text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`, }, ], isError: true, }; } } ); - src/tools.ts:813-831 (handler)The core handler function for the taskGet tool. It takes a task id, calls sendRpcRequest to the backend 'task.get' RPC, stringifies the result as JSON text, and handles errors appropriately.
async ({ id }) => { try { const data = await sendRpcRequest("task.get", [id]); return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }], }; } catch (error) { logger.error("Error fetching task.get: %o", error); return { content: [ { type: "text", text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`, }, ], isError: true, }; } } - src/tools.ts:808-812 (schema)Input schema for taskGet tool using Zod: requires a string 'id' parameter representing the task ID.
{ /* {"$id":"#task-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"} */ id: z.string(), },