Loading ToolBench

Reading the current corpus…

logali-mcp-hana MCP server · C · ToolBench

← Browse

logali-mcp-hana

github.com/logalitech/logali-mcp-hana

MCP server for SAP HANA and HANA Cloud: run read-only SQL, list schemas and tables, and describe table columns.

2026-07-28+STDIO5 tools

62/100

Definition Quality80

Protocol Readiness50

Supportability40

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: stateless requests

Current-spec patterns detected

Summary

Five tools with clear verb-noun naming (list_*, describe_*, run_*, execute_*). All have descriptions (194 - 250 chars, within baseline 34 - 392). Input schemas present with types and constraints. Key strengths: parameter constraints (minLength, minimum/maximum), clear risk labels (READ_ONLY, WRITE), and actionable descriptions. Gaps: no output schemas documented, no error recovery guidance, no tool annotations (readOnlyHint/destructiveHint), and execute_statement lacks confirmation/dry-run pattern for destructive operations.

Tools (5)

describe_tableread onlyauthsource verified82/100

Describe the columns of a table or view using SYS.TABLE_COLUMNS: name, data type, length, scale, nullability and key position, in column order. Read-only.

execute_statementwriteauthsource verified73/100

MUTATING: execute an arbitrary SQL statement (DML or DDL such as INSERT, UPDATE, DELETE, CREATE, DROP). This changes remote state and is disabled by default. It only runs when LOGALI_MCP_ALLOW_WRITE=true. Supports positional parameters (question mark placeholders).

list_schemasread onlyauthsource verified80/100

List database schemas from SYS.SCHEMAS. Optionally filter by owner. Read-only.

list_tablesread onlyauthsource verified83/100

List tables (SYS.TABLES) and views (SYS.VIEWS) in a schema, with type and a cheap row count estimate for tables. Provide schema or rely on HANA_SCHEMA. Read-only.

run_queryread onlyauthsource verified80/100

Run a read-only SQL query against SAP HANA and return columns and rows. Only a single SELECT or WITH statement is accepted; any DML, DDL, procedure call or multiple statements is rejected. Supports positional parameters (question mark placeholders). Results are truncated to maxRows.

Issues (5)

HIGHtool ↗

No output schemas documented. LLMs cannot infer what fields to expect from list_schemas, list_tables, describe_table, run_query, or execute_statement. This forces LLMs to guess at response structure and risks failed downstream tool chaining.

list_schemaslist_tablesdescribe_tablerun_queryexecute_statement

HIGHconfirmation-request ↗

execute_statement (WRITE/MUTATING) lacks confirmation or dry-run pattern. Agents can execute arbitrary DDL/DML without a safety gate. No recovery guidance if a DELETE or DROP succeeds unintentionally.

execute_statement

MEDIUMtool ↗

No tool annotations (readOnlyHint, destructiveHint, idempotentHint). The MCP spec (2026-07-28) supports tool annotations to signal safety properties. list_schemas, list_tables, describe_table, run_query should be marked readOnly=true; execute_statement should be marked destructive=true.

list_schemaslist_tablesdescribe_tablerun_queryexecute_statement

Recommendations

Document output schemas for all five tools. Example for list_schemas: 'Returns array of {schema_name: string, owner: string, created_date: ISO8601}'. This enables LLMs to plan downstream calls and extract the right fields.
Add tool annotations to tool registration. Mark list_schemas, list_tables, describe_table, run_query with readOnlyHint=true. Mark execute_statement with destructiveHint=true. This signals safety properties to MCP clients.
Implement a dry-run or confirmation pattern for execute_statement. Either add a 'dryRun' boolean parameter that returns the execution plan without committing, or require a separate 'confirm_execute' tool that the agent must call after reviewing the statement.
Enhance error messages with recovery guidance. Example: 'SQL syntax error at line 2: unexpected token. Check your SELECT statement and try again.' or 'Permission denied: user lacks INSERT privilege on table ORDERS. Contact your DBA.'
Document SQL validation logic in tool descriptions. Clarify that run_query rejects DML/DDL/procedures via regex or parser, and explain what happens if validation fails (e.g., 'Returns error: Only SELECT and WITH statements are allowed').

Score history

Overall score trend

First recorded score · v2 rubric

62/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	C	62	2026-07-28+	v2