Loading ToolBench
SDK and community blueprints for the Automation Blueprints Marketplace - provides DSL validation, adapters for converting blueprints to multiple automation platforms (Zapier, Make, n8n, Power Automate), and CLI tools
This is not an MCP server, it's a TypeScript SDK/library for blueprint DSL validation and adapter conversion. No MCP protocol implementation detected. Tools are inferred from class methods and functions, not registered via MCP's tool definition mechanism. Input schemas are either missing or use 'unknown' type (18 of 18 tools). Descriptions exist but are generic and lack LLM-optimized guidance. No error handling patterns, no parameter validation, no output schema documentation. The codebase is a standalone npm package, not an MCP server.
Checks if this adapter can handle the given DSL. Optional method for validating runtime-specific constraints before conversion.
Detects DSL features present in the input that this adapter does not translate to its target format.
Converts blueprint DSL JSON into target runtime format.
Retrieves an adapter by its runtime identifier.
Lists all registered adapter runtime identifiers.
Registers a new adapter in the global registry for converting blueprints to platform-specific formats.
Checks if the Make adapter can handle the given DSL based on policy constraints.
Detects DSL features not supported by Make platform (scopes, policies).
Not an MCP server. This is a standalone TypeScript SDK/library with no MCP protocol implementation, tool registration, or transport layer. Cannot be used as an MCP server.
All 18 tools have input schemas with 'unknown' type or missing type definitions. No JSON Schema validation possible.
No output schemas documented. Tools like toTargetFormat return complex objects (ZapierPlatformOutput, MakeScenarioMetadata, etc.) but LLMs have no guidance on expected fields, types, or structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Converts automation blueprint DSL to Make (Integromat) scenario format. Creates a flow array with trigger and action modules, including positioning metadata and parameter mappings.
Checks if the n8n adapter can handle the given DSL based on policy constraints.
Detects DSL features not supported by n8n platform (scopes, retry limits, policies, trigger filters for webhooks/schedules, step outputs).
Converts automation blueprint DSL to n8n workflow format. Creates a workflow with the appropriate trigger node type derived from trigger.app, action nodes for each step, node connections, and expression-based transforms.
Checks if the Power Automate adapter can handle the given DSL based on policy constraints.
Detects DSL features not supported by Power Automate platform (scopes, policies).
Converts automation blueprint DSL to Azure Logic Apps / Power Automate workflow definition schema.
Converts automation blueprint DSL to Zapier Developer Platform JSON format.
Parses a DSL condition string into a structured ParsedCondition. Supports the template reference format {{steps.<stepId>.<field>}} <op> <value> where <op> is a JavaScript-style comparison operator (===, ==, !==, !=, >, >=, <, <=) and <value> is a string literal, numeric literal, or boolean keyword.
Validates an automation blueprint object against the DSL JSON Schema. Checks that the blueprint conforms to the standardized automation blueprint format including required fields (id, name, version, apps, trigger, steps) and optional fields (scopes, retry, policies, fixtures, tests, compatibility).
No error handling or recovery guidance. Tools provide no error messages, validation feedback, or actionable next steps when inputs are invalid or operations fail.
Descriptions are generic and lack LLM-optimized context. Most descriptions (e.g., 'Registers a new adapter') do not explain WHEN to use the tool, WHAT it returns, or HOW it differs from similar tools. Baseline for A+ tools is 50-200 chars with clear intent.