Loading ToolBench
Model Context Protocol server for the Heretto Deploy API. Exposes the Heretto Deploy v4 API as MCP tools for searching and retrieving documentation from a Heretto Deploy deployment.
Heretto Deploy MCP demonstrates solid definition quality with all 10 tools having clear, action-verb names and descriptions. Input schemas are present and properly typed for all tools. However, several tools lack output schema documentation, and parameter descriptions could be more detailed regarding constraints and formats. The server includes thoughtful instructions for link presentation and workflow guidance, which is excellent for LLM usability. Most tools follow the pattern:tool and pattern:tool-description guidelines, but output documentation and error handling guidance are gaps.
Retrieve an API specification document from a Heretto Deploy deployment.
List all available audiences in a Heretto Deploy deployment.
Retrieve a list of content that has changed in a Heretto Deploy deployment.
Retrieve the full content of a documentation topic by path or ID from a Heretto Deploy deployment.
Retrieve metadata about a Heretto Deploy deployment.
List all available locales (languages) in a Heretto Deploy deployment.
Output schemas not documented in tool definitions. LLMs cannot plan downstream calls or extract required fields without knowing what each tool returns.
Parameter descriptions lack format constraints and validation rules. E.g., 'organization_id' and 'deployment_id' have no guidance on format, length, or character restrictions.
No error handling guidance in tool descriptions. LLMs cannot determine what to do if a search returns no results, a deployment is not found, or the API is unreachable.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | <=2025-11-25 | v2 |
Retrieve the current server configuration and connectivity status.
Retrieve the table of contents / navigation structure of a Heretto Deploy deployment.
List source files in the CCMS for a given documentation path.
Search for documentation content in a Heretto Deploy deployment using a query string.
Mutually exclusive parameters not documented. 'get_content' accepts both 'for_path' and 'for_id' but does not state which takes precedence or if both are required.
No pagination parameters (limit, offset, page_size) on tools that likely return lists (search, list_source_files, get_changed_content). Large result sets risk context window exhaustion.