Loading ToolBench
MCP server for Coralogix logs analysis and sequence diagram generation
Server has 5 tools with complete Zod schemas and basic descriptions. All tools are READ_ONLY and follow verb_noun naming (query_logs, search_logs_by_error, find_logs_by_function, generate_sequence_diagram, extract_users_list). However, descriptions are generic (avg ~60 chars) and lack context about when to use each tool vs. alternatives. Parameters have types and descriptions, but lack constraints (enums, ranges, patterns). No output schema documentation. Error handling uses UserError but provides minimal recovery guidance. Missing tool annotations (readOnlyHint explicitly declared). No pagination support despite tools returning potentially large result sets.
Extract a list of users from logs based on a timeframe and query
Find logs related to a specific function
Generate a Mermaid sequence diagram from log entries
Query Coralogix logs using Lucene syntax
Search logs containing specific error messages
Descriptions lack LLM-optimized context. Avg 60 chars; no guidance on when to use each tool vs. alternatives (e.g., query_logs vs. search_logs_by_error). LLMs cannot distinguish intent.
No output schema documentation. Callers cannot predict response structure (e.g., extract_users_list returns {users, totalUniqueUsers, timeframe, query} but this is not documented in tool definition).
No pagination support. Tools return potentially large result sets (logs, users) without limit enforcement or cursor/offset parameters. Large responses risk context window exhaustion.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
Parameters lack constraints. 'timeframe' accepts free-form strings (e.g., 'last 24h', 'last 7d') with no enum or pattern validation. LLMs may hallucinate invalid formats.
Error handling provides no recovery guidance. UserError messages are generic ('Failed to query logs: <error>') and do not suggest next steps or alternatives.