PeerDB MCP

diagnose_pipeline

Read-onlyIdempotent

Inspect a PeerDB pipeline's status, recent errors, and CDC batches, then get heuristic troubleshooting steps; returns partial results if a check fails.

Instructions

Combine status, recent errors and CDC batches with heuristic troubleshooting steps.

Reports partial results if a check fails. Never repairs or changes a pipeline.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing that partial results are returned when a check fails and that no repair is attempted. These are behavioral traits not captured by the annotations.

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?

Two tight sentences with the core diagnostic purpose front-loaded and the failure/read-only caveats following. No filler; every clause carries meaning.

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?

An output schema exists, so return-format details are not required, and the description covers the key edge case (partial results on failure) plus the non-mutating guarantee. The main remaining gap is that neither parameter is described.

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

Parameters2/5

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

Schema description coverage is 0% and the description says nothing about either parameter. It never explains what 'name' identifies (pipeline name) or what 'limit' bounds (e.g., error/batch rows), so it fails to compensate for the undocumented schema.

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 (diagnose) and resource (pipeline) and clarifies it aggregates status, recent errors, and CDC batches into heuristic troubleshooting. This distinguishes it in substance from the sibling single-fetch tools (get_pipeline_status, get_pipeline_errors, get_pipeline_batches), though it never names them explicitly.

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?

'Never repairs or changes a pipeline' signals the read-only diagnostic role and implicitly points write actions to update/resume/pause siblings, but there is no explicit statement of when to reach for this aggregate tool versus the granular get_* siblings. Usage is implied rather than spelled out.

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

Deploy Server