Loading ToolBench
MCP Server for Data Engineering Knowledge - provides tools to fetch recent Data Engineering updates, manage user knowledge memory, and deliver personalized learning content
Three tools with basic definitions but significant gaps in schema completeness, parameter descriptions, and error handling guidance. Tool names follow verb-noun pattern but descriptions lack depth. No parameters have type constraints or detailed guidance. No output schemas documented. Error handling is absent. This server would require substantial rework before production use.
Fetches recent news and updates about Data Engineering concepts, patterns, and technologies using Perplexity Sonar via OpenRouter.
Reads the user's current Data Engineering knowledge from memory.
Updates the user's Data Engineering knowledge memory for a specific concept.
No output schemas documented for any tool. LLMs cannot infer what fields to expect in responses, forcing them to guess downstream field names and risk extraction errors.
Missing descriptions for input parameters. 'concept' parameter in de_tutor_write_memory lacks guidance on valid concept names. 'known' boolean lacks clarification on whether true means 'user knows' or 'user learned'.
de_tutor_read_memory and de_tutor_write_memory have empty input schemas ({}). Empty schemas provide zero guidance to LLMs about parameter constraints, valid values, or format expectations.
Tool descriptions are generic and lack context. 'Reads the user's current Data Engineering knowledge from memory' does not explain when to use this vs other tools, what structure the memory returns, or why it matters for the workflow.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 43 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | - | v1 |
No error handling or recovery guidance. If API calls fail, no guidance on whether to retry, ask the user, or proceed with cached data. If a concept is unknown, no error message or fallback.
de_tutor_write_memory exposes OpenRouter API integration risk. If the external API is unreachable, tool fails silently with no guidance. Consider wrapping external calls with explicit error handling and user-facing messages.
No parameter validation or constraints. 'concept' in de_tutor_write_memory accepts any string, no enum of valid concepts, no length limits, no format guidance. LLMs will pass arbitrary strings.