Skip to main content
Glama

mnemon_configure_pooler

Inspect or configure PgBouncer pooling mode and maximum backend connections for a database tenant, enabling control over connection limits and pooling behavior.

Instructions

Inspect or configure PgBouncer connection pooling mode and max connection limits.

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>"
    },
    "name": "mnemon_configure_pooler"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_modeNoPooling mode
tenant_idYesDatabase tenant identifier
max_pool_sizeNoMaximum pooled backend connections

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the whole burden and falls well short: it does not say whether changing pool_mode or max_pool_size disrupts live connections, whether the change is immediate or requires reload, whether it is reversible, or what permissions are needed. The one useful signal it does carry implicitly is that the tool both reads and mutates configuration, which is why this is not a 1.

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 filler or redundancy. It is efficient, though the brevity comes partly from omitting information rather than from tight editing.

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

Completeness2/5

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

For a configuration mutation tool with no annotations, no output schema, and a dual inspect/configure contract, the description should explain the read-vs-write semantics, side effects on existing connections, and what a successful inspection returns. None of that is present, so an agent could invoke it safely only by guessing.

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 baseline is 3; the schema already names pool_mode with its transaction/session enum, tenant_id, and max_pool_size. The description adds only the PgBouncer framing and confirms the parameters are per-tenant, but supplies no units, ranges, or defaults for max_pool_size and no explanation of how pool_mode interacts with it.

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 pair ("Inspect or configure") and a specific resource ("PgBouncer connection pooling mode and max connection limits"), so an agent knows the domain is connection-pool configuration for a tenant. It does not differentiate itself from the sibling configuration tools (mnemon_configure_scaling, thanaton_configure_scaling), but the resource is distinctive enough that confusion is unlikely.

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?

The phrase "inspect or configure" hints at a dual read/write mode but never explains how each is selected, nor what prerequisites (tenant state, permissions, active connections) must hold. There is no when-to-use guidance and no exclusion or alternative named, leaving the agent to guess whether omitting optional fields yields a read or a no-op write.

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