Skip to main content
Glama

mnemon_manage_extensions

List, enable, or disable PostgreSQL extensions such as vector, pg_search, postgis, and uuid-ossp for a tenant database.

Instructions

Manage 1-click PostgreSQL extensions (vector, pg_search, postgis, uuid-ossp).

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": {
      "tenant_id": "<tenant_id>",
      "action": "<action>"
    },
    "name": "mnemon_manage_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExtension name (for enable/disable)
actionYesAction to perform
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that enable/disable mutate the database, whether changes require elevated permissions, whether a restart or lock is involved, or whether the operation is reversible. Only the generic 'Manage' hints at mutation.

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?

A single front-loaded sentence with no wasted words. It is appropriately sized, but the brevity reflects under-specification of behavior rather than tight, complete communication.

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

Completeness3/5

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

For a three-parameter tool with full schema coverage, the definition is minimally usable. However, with no annotations and no output schema, the description leaves gaps around what 'list' returns, what happens on enable/disable, and any permission requirements.

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%, so tenant_id, action (with enum), and name are already documented in the schema. The description adds value only by enumerating the supported extension names, which the schema does not list; otherwise it adds no meaning beyond the schema baseline.

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

Purpose3/5

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

The description names a specific resource (PostgreSQL extensions) and gives concrete examples (vector, pg_search, postgis, uuid-ossp), which helps ground it. But the verb 'Manage' is generic and does not reveal the actual operations available (list/enable/disable), so an agent must open the schema to learn what it can do. It is distinguishable from siblings by resource, but only minimally informative about the action.

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

Usage Guidelines2/5

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

There is no statement about when to use this tool, when not to, or which sibling to prefer. The '1-click' phrasing hints at convenience but implies no prerequisites, permissions, or conditions for enabling versus disabling.

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