Loading ToolBench
MCP server providing access to MeetingBaas documentation, GitHub repositories, and utility tools. Deployed on Vercel with support for HTTP and SSE transports.
This server exhibits poor definition quality across multiple dimensions. While 19 tools are explicitly registered with descriptions, the schema definitions are minimal or absent, parameter descriptions are generic, and output documentation is completely missing. The tool set is notably redundant (15 documentation retrieval tools with heavily overlapping functionality), and the majority of tools accept zero parameters, making them discovery-oriented rather than composable. The descriptions, while present, are generic one-liners that fail to guide LLM selection or explain dependencies. No output schemas are documented, and error handling recovery paths are not defined.
Echo a message with a Documentation Helper prefix
Get all MeetingBaas documentation content
Get MeetingBaas API documentation
Get Calendars API documentation
Get documentation by category name
Get Meetings API documentation
Get README.md file from a specific Meeting-Baas GitHub repository
Get MeetingBaas SDK documentation
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract data when return types are unknown.
Severe tool redundancy: 15 separate documentation retrieval tools (getApiDocs, getCalendarsDocs, getMeetingsDocs, etc.) should consolidate into getDocsByCategory with enum-driven selection. This forces LLMs to waste reasoning cycles disambiguating between nearly identical tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Get Speaking Bots documentation
Get Transcript Seeker documentation
Get Bot-related TypeScript SDK documentation
Get Calendar-related TypeScript SDK documentation
Get Common TypeScript SDK methods and types documentation
Get TypeScript SDK documentation
Get Webhook-related TypeScript SDK documentation
Get Users API documentation
Get Webhooks API documentation
List all available MeetingBaas documentation categories
List all publicly available GitHub repositories from Meeting-Baas organization
Generic descriptions that do not guide LLM selection. Examples: 'Get all MeetingBaas documentation content', 'Get MeetingBaas SDK documentation'. These fail to distinguish when to use getAllDocs vs getSdkDocs, or explain prerequisites and output structure. Average description length ~35 chars (below baseline of 194 chars).
getDocsByCategory has an enum constraint on the 'category' parameter (good), but the description of the category parameter itself is generic ('The documentation category to fetch'). Should explain what each category contains and when to use list vs getDocsByCategory.
Most tools (14 of 19) accept zero parameters and simply return all content for a category. No pagination, no filtering, no limit controls. If a category returns thousands of docs, the LLM context window is exhausted. No limit is stated in descriptions.
No error handling recovery guidance. If getRepositoryReadme is called with a non-existent repository name, what does it return? Does it suggest similar repo names? Agents need actionable error messages.
docHelpAssistant is a utility/test tool (echo prefix message). Its name does not start with a clear verb phrase suggesting it retrieves help documentation. The name 'docHelpAssistant' with action 'echo a message' is semantically mismatched and risks LLM confusion about its purpose.
No composition hints. If an LLM calls listCategories, the response should guide it toward getDocsByCategory. If getRepositoryReadme fails, the response should suggest listRepositories. Current tools offer no discovery or relationship hints.