Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-search

Read-onlyIdempotent

Search PostgreSQL databases by query, name, description, app, project, or environment, and paginate results to locate the instance you need.

Instructions

GET /postgres.search

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": "postgres-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
offsetNo
appNameNo
projectIdNo
descriptionNo
environmentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description owes context such as result shape, pagination behavior, or search semantics. Instead it adds nothing beyond the HTTP verb, and reveals no behavioral trait the annotations do not already state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than efficiency; a bare URL fragment is not front-loaded prose that conveys purpose. There is no structure an agent can parse into intent.

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

Completeness1/5

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

For an eight-parameter, untyped search endpoint with no output schema and no field documentation, the description is completely inadequate. Everything an agent needs in order to call it correctly is absent.

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

Parameters1/5

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

Schema description coverage is 0% across eight parameters, and the description supplies no meaning for q, name, limit, offset, appName, projectId, description, or environmentId. With none required and no documented semantics, an agent cannot know how to build a meaningful query.

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

Purpose2/5

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

"GET /postgres.search" only restates the tool name as an HTTP verb plus path, with no statement of what is searched or what is returned. An agent cannot distinguish this from siblings like mariadb-search, mysql-search, or application-search beyond the database engine implied by the prefix.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no mention of prerequisites such as picking a project, app, or environment. The eight sibling search tools are left entirely unaddressed.

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