A simple Altibase MCP server that provides SQL tools and resources for interacting with an Altibase database
Server has 6 tools with basic descriptions and schemas, but significant gaps limit production readiness. Tool names follow verb_noun convention (read_query, write_query, create_table, list_tables, describe_table, append_insight), which is good. However, descriptions are generic and lack actionable context for LLM selection. Input schemas are present but minimal, most parameters are bare strings with no format constraints, enums, or validation guidance. No output schemas documented. Error handling is absent from visible code. Security concerns: write_query and create_table accept raw SQL strings with no injection protection or confirmation step. The append_insight tool mixes database operations with memo management, violating single-responsibility principle.
Adds a new business insight to the memo resource
Creates new tables in the database
Shows the schema for a specific table
Shows all existing tables
Executes SELECT queries to read data from the database
Executes INSERT, UPDATE, or DELETE queries to modify data
No input validation or SQL injection protection. write_query and create_table accept raw SQL strings without sanitization, allowing prompt-injection attacks to execute arbitrary database commands.
Missing output schemas. No documentation of what read_query, list_tables, or describe_table return. LLMs cannot plan downstream tool calls or extract structured data without knowing response fields.
No error handling or recovery guidance. Code does not show try-catch blocks, error categorization, or actionable error messages. LLMs receive raw exceptions with no guidance on retry vs. user-fixable vs. fatal.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | <=2025-11-25 | v2 |
Irreversible operations lack confirmation step. create_table and write_query (DELETE) can destroy data without dry-run or confirmation. Agents make mistakes, no safeguard prevents catastrophic errors.
append_insight violates single-responsibility principle. Tool mixes memo resource management with business logic. Should be split: one tool to append insights, separate resource for memo retrieval.