Scribase

import.postgres

Import a plain Postgres database (Neon, Render, RDS, self-hosted) into an environment. POST /v1/imports. Only a connection string is needed: unlike Supabase, there is no platform API alongside the database, so no service key or storage is asked for. With dry_run true it reports what would move and changes nothing; without it the import starts in the background (so requires confirm) and returns an import_id to follow with import.status.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>",
      "source_connection_string": "<source_connection_string>",
      "confirm": "<confirm>"
    },
    "name": "import.postgres"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`dry_run`	No	Report only, do not migrate (default false)
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`source_schemas`	No	Comma-separated schema names to copy (default: every non-system schema)
`organization_id`	Yes	organization_id (required)
`source_connection_string`	Yes	source_connection_string (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false and non-idempotent, so the bar is lower; the description still adds real behavior: that the non-dry path runs in the background, requires confirm, and returns an import_id to track via import.status. It does not say what happens to pre-existing data in the target environment, which matters for an import tool claiming destructiveHint=false.

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?

Four front-loaded sentences: purpose and supported sources first, then the distinguishing constraint, then the two execution modes. Dense but every clause carries information; only the Supabase comparison is slightly parenthetical.

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

Completeness5/5

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

For a mutating, long-running import with no output schema, the description covers the decision inputs (which Postgres flavors), the safety path (dry_run changes nothing), the confirmation requirement, and the return value (import_id plus the follow-up tool). Little an agent needs to call this correctly is missing.

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 coverage is 100%, so the schema already documents all seven parameters, and the description's confirm/dry_run commentary largely restates the schema wording. It adds the useful framing that a connection string is the only connection material needed, but nothing about source_schemas or the id formats beyond what the schema says, so the baseline 3 holds.

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 ("Import a plain Postgres database") plus the supported source variants (Neon, Render, RDS, self-hosted), and it explicitly contrasts itself with the sibling import.supabase. An agent can route between import.postgres and import.supabase from the text alone.

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

Usage Guidelines4/5

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

"Only a connection string is needed: unlike Supabase, there is no platform API alongside the database" gives a clear condition that selects this tool over the named alternative, and the dry_run sentence sets up the preview-vs-real decision. There is no explicit "do not use this for Supabase" instruction or prerequisite checklist, so it stops just short of a 5.

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

All Scribase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?