Loading ToolBench
ArchiPulse — ArchiMate workspace management. Exposes ArchiPulse workspace data as tools that Claude can call.
ArchiPulse exposes 14 well-named tools with consistent verb_noun patterns (list_, get_, create_). All tools have descriptions (avg ~80 chars, within baseline 34 - 392). Input schemas are present and typed for all tools. However, parameter descriptions are minimal (often just 'Workspace UUID' or 'Page number'), lacking actionable guidance on constraints, ranges, or dependencies. Output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling is absent from visible code. No tool annotations (readOnlyHint/destructiveHint). Pagination is implemented but lacks total_count or next_cursor guidance in descriptions. Overall: solid foundation, but descriptions and output documentation need expansion to reach production grade.
Create a new ArchiMate workspace
Get the application catalogue — all applications with lifecycle status, capabilities, and technology details
Get application statistics dashboard for a workspace
Get the capability tree — hierarchical breakdown of business capabilities
Get the application dependency graph — nodes and edges showing how applications depend on each other
Get a specific diagram
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for downstream tool chaining. E.g., get_workspace returns what fields? Does list_elements return element_id for use in get_element?
Parameter descriptions lack actionable constraints. 'Page number (default 1)' does not specify min/max range. 'Results per page (default 50, max 500)' mentions max in description but not as a formal constraint. LLMs cannot validate inputs without explicit bounds.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Get an ArchiMate element with all its properties grouped by source
Get the integration map — application-to-application data flows and interfaces
Get a specific ArchiMate relationship
Get details of a specific workspace
List diagrams in a workspace (paginated)
List ArchiMate elements in a workspace (paginated)
List ArchiMate relationships in a workspace (paginated)
List all ArchiMate workspaces the current user has access to
No error handling guidance in visible code. If workspace_id is invalid or user lacks permission, what error is returned? How should the LLM recover? No recovery guides or error classification.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe read-only tools from destructive ones. create_workspace is WRITE but unmarked; list_* are READ_ONLY but unmarked.
Pagination descriptions do not mention total_count or next_cursor. LLMs cannot determine if more results exist or how to fetch them efficiently. Baseline pattern requires pagination metadata in response.