MCP server providing database connectivity and query tools for Salesforce via ODBC, with support for schema introspection, data manipulation, and routine execution
14 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Most tools have 1-3 parameters with type info, but descriptions are minimal (10-50 chars). No tool annotations (readOnlyHint/destructiveHint). Error handling and recovery guidance absent. Naming is verb-forward (get_, execute_, add_) but some tools like 'config' and 'instructions' lack clarity on purpose. Output schemas not documented, LLMs cannot predict response structure for chaining. No pagination support despite tools returning lists (get_tables, get_columns, get_routines). Security concern: execute_nonquery and execute_routine accept arbitrary SQL/parameters with no validation hints.
Adds a new row to a specified table
Configuration tool for the server
Counts the number of rows in a specified table
Executes SQL statements with supported operations (INSERT, UPDATE, DELETE, etc.)
Executes one or more SQL-92 SELECT statements and returns results
Executes a stored procedure or function
Retrieves list of columns for a specified table
Retrieves foreign key information for a specified table
No output schemas documented. LLMs cannot predict response structure (field names, types, nesting) for downstream tool chaining. E.g., get_tables returns what? Array of strings? Objects with schema/name/type? Unknown.
execute_nonquery and execute_routine accept arbitrary SQL and parameters with no validation hints, constraints, or error recovery guidance. LLMs cannot know what SQL is safe or how to handle failures. No dry-run or confirmation pattern for destructive operations.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without parsing descriptions. execute_nonquery and add_row should be marked destructive; get_* tools should be marked read-only.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Retrieves list of indexes for a specified table
Retrieves primary key information for a specified table
Retrieves list of stored procedures and functions
Retrieves list of tables from the database schema
Instructions tool providing embedded documentation
Retrieves the database server version information
Parameter descriptions are minimal (10-50 chars). E.g., 'Name of the schema' lacks context: is schema required? What if omitted? What are valid schema names? Descriptions should be 50-200 chars with constraints and examples.
No pagination support. Tools returning lists (get_tables, get_columns, get_routines) lack limit, offset, and total_count. Large result sets will blow context windows. No guidance on result limits.