Skip to main content
Glama

mnemon_cdc_stats

Inspect PostgreSQL CDC streaming health by tenant, showing real-time buffer saturation and subscriber lag to diagnose replication delays.

Instructions

Inspect PostgreSQL real-time Change Data Capture (CDC) streaming stats, buffer saturation, and subscriber lag.

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_cdc_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/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 hints at what data is surfaced but never states that it is read-only, whether it has side effects, permission requirements, or whether it hits the live database. Subscriber lag and buffer saturation are listed without any behavioral implications.

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?

One front-loaded sentence with no redundant or filler wording; every clause adds a distinct piece of information about what is inspected.

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 one-parameter read tool with no output schema this is borderline adequate. It could say more about what the returned stats contain or how the tenant scopes results, but the listed metrics give an agent a rough idea of the payload.

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?

There is a single tenant_id parameter fully described in the schema (100% coverage), so the schema already does the explanatory work. The description adds nothing about tenant scoping, so baseline 3 applies.

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 (Inspect) and a specific resource (PostgreSQL real-time CDC streaming stats), plus the sub-metrics covered (buffer saturation, subscriber lag). The read-oriented 'Inspect' framing distinguishes it from the write-oriented sibling mnemon_cdc_publish without naming it.

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?

The diagnostic intent is implied by 'Inspect ... stats', suggesting use during monitoring or troubleshooting, but the description never states when to use it versus alternatives or any preconditions such as tenant scope.

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