SQL Optimiser

Analyse a SQL query for performance. Returns a rewritten query, index suggestions and what each change improves.

Pay by wallet (x402) AI-generated sql-optimize

Example

Example answer
{
  "dialect": "postgres",
  "explanation": "The provided SQL query 'test' is not a valid SQL statement. Please provide a valid SELECT, INSERT, UPDATE, or DELETE query for optimization analysis.",
  "changes_made": [],
  "original_sql": "test",
  "optimized_sql": "Unable to optimize - invalid input provided",
  "estimated_improvement": "N/A",
  "index_recommendations": []
}

Inputs

FieldTypeRequiredWhat it is
sqlstringYes—
dialectstringNo—
table_schemastringNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
improvementsarrayAlways (present in every successful answer)
optimized_sqlstringAlways (present in every successful answer)
estimated_improvementstringAlways (present in every successful answer)
index_recommendationsarrayAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "sql-optimize",
    "inputs": {
      "sql": "SELECT * FROM users WHERE active = true LIMIT 10",
      "dialect": "postgres",
      "table_schema": "users(id INT, name TEXT, email TEXT, active BOOL, created_at TIMESTAMP)"
    },
    "max_price_cents": 5
  }'

Limitations

  • Performance gains depend on your database

    Optimisation suggestions are generic — actual performance gains depend on your database engine, data size, and index configuration

    What to do instead: Benchmark the suggested queries with EXPLAIN ANALYZE against your own data.