Skip to main content
Glama

Remove a PostgreSQL extension

disable_extension
DestructiveIdempotent

Drops the extension without CASCADE: if objects depend on it, it stays and get_database shows why in warning. 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": "disable_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe logical database.
databaseYesDatabase id, as returned by list_databases or create_database.
extensionYesName of an extension enabled in that logical database (see get_database).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / extension / description
      Added value: +"Name of an extension enabled in that logical database (see get_database)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the safety profile is covered. The description still adds real value beyond them: the absence of CASCADE, the resulting behavior when dependents exist (the extension 'stays'), where the reason surfaces (a warning from get_database), and the required scope 'databases.write'. It stops short of saying what happens to dependent objects or what the immediate response contains, which is the remaining gap.

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

Conciseness4/5

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

Two short sentences, no filler, with the consequential behavior (no CASCADE) front-loaded before the scope note. The clause 'it stays and get_database shows why in warning' is grammatically compressed to the point of being slightly hard to parse, which costs a point on structure but not on economy.

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 three-parameter destructive mutation with full schema coverage and no output schema, the definition covers the essentials: destructiveness, the no-CASCADE contract, the failure mode, the diagnostic route, and the required scope. What is missing is the success-side outcome — whether the extension is dropped immediately and what the caller sees on success — but the safety-critical information an agent needs before invoking it is present.

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 description coverage is 100%, and all three parameters carry their own descriptions including how to obtain database id and extension name. The description adds only an implicit cross-reference to get_database for verifying the extension exists; it contributes no additional format, naming, or constraint detail. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource — 'Drops the extension' — and immediately narrows it with 'without CASCADE', which is the operative detail. It does not name the sibling enable_extension or explain the disable-vs-drop naming, so the name/title mismatch ('disable_extension' / 'Remove') is only resolved by the description body rather than by explicit 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 is implied rather than stated: the no-CASCADE note tells the agent this is the conservative removal path, and 'get_database shows why in warning' points to the diagnostic follow-up. There is no explicit statement of when to prefer this over dropping with CASCADE, nor any precondition such as ownership or extension existence, so an agent must infer the selection criteria.

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.