Skip to main content
Glama

Enable a PostgreSQL extension

enable_extension
Idempotent

PostgreSQL only. Enables an extension from get_database_options (vector for pgvector, postgis, pg_trgm…) in one logical database; installed on demand, live within a minute. Scope: databases.write.

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": {
      "database": "<database>",
      "name": "<name>",
      "extension": "<extension>"
    },
    "name": "enable_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe logical database, e.g. defaultdb.
databaseYesDatabase id, as returned by list_databases or create_database.
extensionYesExtension name from get_database_options, e.g. vector, postgis, pg_trgm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / extension / description
      Added value: +"Extension name from get_database_options, e.g. vector, postgis, pg_trgm."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the operation is not read-only, is idempotent, and is non-destructive. The description adds valuable operational context: PostgreSQL only, single logical database scope, installed on demand, live within a minute, and requiring databases.write. This goes meaningfully beyond the annotations without contradicting them.

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

Conciseness5/5

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

The description is short, front-loaded with the PostgreSQL constraint, and every clause carries useful information: source of extension names, scope, provisioning behavior, timing, and required permission scope. There is no redundant or filler text.

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 non-destructive, idempotent mutation tool with no output schema, the description supplies the key facts an agent needs: platform restriction, valid extension source, database scope, provisioning latency, and authorization scope. It is nearly complete; only explicit error or unsupported-extension behavior is absent.

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

Parameters3/5

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

Schema coverage is 100%, so the input schema already documents the database, name, and extension parameters fully. The description reinforces that extension names come from get_database_options and must target one logical database, but adds little beyond the schema's own examples and constraints. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

The description states a specific verb and resource: enabling a PostgreSQL extension in one logical database. It references get_database_options as the source of valid extension names, which helps distinguish discovery from activation. It is clear but does not explicitly contrast with disable_extension, so it falls short of the strongest sibling differentiation.

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

Usage Guidelines3/5

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

Usage context is implied: use this to turn on an extension whose name comes from get_database_options. The PostgreSQL-only constraint is useful. However, it does not explicitly state when not to use it or call out disable_extension as the inverse operation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.