Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Enable Engine Insights

enableEngineInsights
Destructive

Turns on database engine insights reported as off, enabling Postgres pg_stat_statements and slow-query logging plus MySQL/MariaDB statement history and deadlock diagnostics without resetting counters.

Instructions

Turns on what streamEngineStats lists as off. Postgres: adds pg_stat_statements to shared_preload_libraries and restarts the service, then creates the extension in the postgres database on a second call, and logs statements slower than 250 ms with lock waits, through ALTER SYSTEM. MySQL and MariaDB: the statement history consumer and deadlock printing at runtime, and on MariaDB user statistics. Never resets any counter.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>",
      "serviceName": "<serviceName>"
    },
    "name": "enableEngineInsights"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
serviceNameYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the most consequential behavior: Postgres requires modifying shared_preload_libraries and restarting the service, a second call is needed to create the extension, config is applied via ALTER SYSTEM, and counters are never reset. The service restart is exactly the kind of side effect an agent must know before invoking a destructiveHint tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries information, but the description is a single dense run-on with clipped syntax ('the statement history consumer and deadlock printing at runtime, and on MariaDB user statistics') that is hard to parse quickly. It would benefit from splitting the Postgres and MySQL/MariaDB behaviors into separate sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, multi-engine tool with no output schema, the behavioral picture is nearly complete: per-engine effects, restart implication, two-call Postgres flow, and non-destructive-to-counters guarantee. The remaining gap is the complete absence of parameter guidance for identifying the target service.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters (workspaceSlug, appSlug, serviceName, env, region), and the description adds no meaning for any of them. It never states that env/region select the target instance or how serviceName must be identified for a restarting operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turns on what streamEngineStats lists as off') and then enumerates exactly what gets enabled per engine (pg_stat_statements, statement history consumer, deadlock printing, MariaDB user statistics). The reference to the sibling streamEngineStats makes the division of labor immediately clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied strongly: run streamEngineStats first to see what is off, then call this to turn it on. It also warns that Postgres extension creation happens 'on a second call', which is genuinely actionable sequencing guidance. No explicit when-not-to-use or prerequisite (permissions) statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools