This server has 3 tools with moderate definition issues. postgrestRequest has a reasonable schema with typed parameters (method enum, path string, body union), but descriptions are generic and lack guidance on when to use each tool. sqlToRest has minimal description (23 chars) and a trivial single-parameter schema. echo is a debug/demo tool with bare-bones definition. None of the tools provide output schemas or error guidance. Parameter descriptions are present but lack actionable constraints. The server does not follow verb-noun naming conventions consistently (postgrestRequest is camelCase, not verb_noun). No tool describes side effects, idempotency, or recovery paths. Overall, definitions are functional but well below production quality.

• Rename postgrestRequest to make_postgrest_request (verb_noun convention). Rename sqlToRest to convert_sql_to_rest.
• Expand postgrestRequest description to 100-150 chars: 'Execute an HTTP request against a PostgREST API endpoint. Use POST for inserts (body = row object), PUT for full updates, PATCH for partial updates, GET to fetch data, DELETE to remove records. Returns the API response body and status code. Requires valid PostgREST URL and API key in Authorization header.'
• Expand sqlToRest description: 'Convert a SQL SELECT/INSERT/UPDATE/DELETE query into an equivalent PostgREST method and path. Useful for translating SQL logic into REST calls. Returns {method: string, path: string}. Supports PostgreSQL dialect. Does NOT execute the query, use make_postgrest_request to run it.'
• Document output schemas explicitly. For postgrestRequest, return {status: number, body: object | array, headers: object}. For sqlToRest, return {method: 'GET'|'POST'|'PUT'|'PATCH'|'DELETE', path: string}.
• Add destructiveHint and idempotentHint annotations to tool options. Mark DELETE operations with destructiveHint=true and confirm_before_execute guidance. Mark GET with idempotentHint=true.
• Add parameter-level guidance for method enum: 'HTTP method. GET to fetch records, POST to insert, PUT for full-record replace, PATCH for field updates, DELETE to remove. Mutation (POST/PUT/PATCH/DELETE) requires request body.'
• Add body parameter schema: 'For POST/PUT/PATCH: a JSON object (single row) or array of objects (bulk). Columns become keys; values are typed (string, number, boolean, null).'