Loading ToolBench
DeepPath MCP server for Anthropic integration - provides tools for managing tasks, goals, notes, automations, and calendar events in a project management system
22 tools with consistent verb-noun naming (get_, create_, update_, delete_) and descriptions present for all. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. similar ones. Input schemas are properly typed with enums for constrained fields (status, repeatPattern), but output schemas are completely undocumented, LLMs cannot plan downstream calls or extract required fields. Parameter descriptions exist but are minimal (avg ~40 chars vs. baseline 72). No error handling guidance, no recovery paths, no confirmation patterns for destructive operations. Security: API key correctly injected via environment variable, but no permission gates or audit trail patterns visible.
Create a new automation rule. Call this when the user wants to set up, create, or establish a new automation, scheduled task, or recurring action.
Create a new calendar event. Call this when the user wants to schedule, create, or add a new event, meeting, or activity to their calendar.
Create a new goal. Call this when the user wants to set, create, or establish a new goal, objective, or milestone.
Create a new note. Call this when the user wants to jot down, write, save, or create a new note, memo, or written record.
Create a new task. Call this when the user asks to add, create, or set up a new task or to-do item.
Delete an automation rule. Call this when the user wants to remove, delete, or get rid of a specific automation.
Output schemas completely undocumented. No tool documents what fields it returns, forcing LLMs to guess structure and plan downstream calls blindly. Violates pattern:tool and pattern:response-shaper.
Destructive operations (deleteTask, deleteGoal, deleteNote, deleteAutomation, deleteCalendarEvent) lack confirmation or dry-run patterns. No error guidance on recovery. Agents can accidentally delete data without safeguards.
Descriptions are generic and do not explain WHEN to use each tool vs. similar ones. E.g., getTasks vs. getTask both retrieve tasks but descriptions don't clarify the distinction. Descriptions avg ~60 chars vs. baseline 194 chars.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Delete a calendar event. Call this when the user wants to remove, delete, or cancel a specific calendar event.
Delete a goal. Call this when the user wants to remove, delete, or get rid of a specific goal.
Delete a note. Call this when the user wants to remove, delete, or get rid of a specific note.
Delete a task. Call this when the user wants to remove, delete, or get rid of a specific task.
Get a list of automations. Use this when the user asks about their automation rules, scheduled tasks, or recurring actions.
Get a list of calendar events. Use this when the user asks about their calendar, events, meetings, or scheduled activities.
Get a list of goals. Use this when the user asks about their goals, objectives, targets, or when discussing project progress and planning.
Get a list of notes. Use this when the user asks about their notes, memos, or written information they've saved.
Get information about the current project. Use this when you need basic project details like name, ID, or general information to provide context.
Get details of a specific task. Use this when the user asks about a particular task by ID or when you need comprehensive information about one specific task.
Get a list of tasks from the project. Use this when the user asks about their tasks, to-do items, or when you need to show task status or overview information.
Update an existing automation rule. Use this when the user wants to modify, adjust, edit, or change an automation.
Update an existing calendar event. Use this when the user wants to modify, reschedule, edit, or change a calendar event.
Update an existing goal. Use this when the user wants to modify, adjust, edit, or change the status or progress of a goal.
Update an existing note. Use this when the user wants to edit, modify, or change the content or title of a note they've already created.
Update an existing task. Use this when the user wants to modify, change, edit, or mark a task as complete.
No pagination support visible in list tools (getTasks, getGoals, getNotes, getAutomations, getCalendarEvents). No limit enforcement or next_cursor pattern. Large result sets will blow context windows.
No permission gates or audit trail patterns. Tools accept no user/agent context. No scope declarations (read:tasks, write:goals, etc.). Cannot enforce least-privilege or trace who called what.