Skip to main content
Glama

Search settings

pg_settings
Read-onlyIdempotent

Search PostgreSQL configuration parameters to inspect current and default values, value sources, restart requirements and pending restarts, configuration errors, and database or role overrides.

Instructions

Search server configuration parameters (GUCs): current value with unit, default, where the value comes from (default, configuration file with line, ALTER SYSTEM, ...), whether changing it needs a restart, whether a restart is pending, and a short description. Also lists errors found in the configuration files and the per-database and per-role overrides (ALTER DATABASE/ROLE ... SET).

pattern matches parameter names (and descriptions), with * wildcards; category filters by group (for example "Write-Ahead Log"); changed_only hides parameters still at their default; pending_restart_only shows what waits for a restart.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pg_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
patternNo
categoryNo
connectionNo
changed_onlyNo
pending_restart_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results reflect live server state, include config-file errors, and surface per-database and per-role ALTER DATABASE/ROLE overrides. It does not mention privilege requirements or output size/pagination behavior.

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 tight blocks: the first front-loads what the search returns, the second maps filters to behavior. Every sentence carries information and the backtick parameter references are easy to scan. The opening inventory is dense but each item earns its place as return-value detail that no output schema provides.

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?

This is a read-only search tool with six parameters, no output schema, and no required params; the description compensates well by describing both the returned fields and four filter behaviors. What is missing is meaningful for a database tool: the semantics of `connection` (which server/database is queried) and how `limit` truncates results.

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

Parameters4/5

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

With 0% schema description coverage, the description has to carry all parameter meaning, and it does for four of six: `pattern` matches names and descriptions with `*` wildcards, `category` filters by group with a concrete example ('Write-Ahead Log'), `changed_only` hides default-valued parameters, and `pending_restart_only` restricts to restart-pending items. `limit` and `connection` are left undocumented, which is a real gap for a multi-connection tool, so it falls short of full compensation.

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 — 'Search server configuration parameters (GUCs)' — and enumerates what each result carries (current value with unit, default, source, restart requirement, description). This is clearly distinct from any sibling like pg_health_check or pg_activity, so an agent can pick it without opening the schema.

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 through the filter parameters (use `changed_only` to hide defaults, `pending_restart_only` to see what waits for a restart), which tells an agent how to narrow a search. However, there is no explicit 'use this when…' framing and no alternative tool is named for postgres configuration questions, so the guidance remains inferential.

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