Skip to main content
Glama

mnemon_import_database

Import or migrate a PostgreSQL database from Neon, Supabase, or AWS RDS into a destination tenant using a source connection URI, with zero-downtime one-click execution.

Instructions

Initiate zero-downtime 1-click database migration/import from Neon, Supabase, or AWS RDS.

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>",
      "source_url": "<source_url>"
    },
    "name": "mnemon_import_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDestination database tenant identifier
source_urlYesSource PostgreSQL connection URI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.1/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, yet it only offers the marketing claims 'zero-downtime' and '1-click'. It does not say whether a replication job is created, what permissions or credentials are needed for the source, whether the source stays live, or how to track progress afterward — all critical for an operation that migrates a production database.

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?

A single front-loaded sentence with no redundancy. The phrase '1-click' is promotional filler that does not help an agent decide or invoke, which keeps it from a 5.

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

Completeness2/5

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

For a state-changing import with no annotations and no output schema, the definition leaves too much unsaid: what the call returns (a job id?), whether it is reversible, and what the follow-up cutover and status calls are for. An agent could invoke it but would not know what to do next.

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 both parameters are already documented in the input schema. The description adds only a small amount by implying that source_url must be a PostgreSQL URI from one of the three named providers; baseline 3 is appropriate.

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?

The description gives a specific verb ('Initiate ... migration/import') plus the resource (database) and names the supported sources (Neon, Supabase, AWS RDS). It is clear what the tool does on its own, though it never distinguishes itself from the adjacent mnemon_import_cutover or mnemon_import_status steps.

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 only implied by the word 'Initiate', which suggests this is the first step in a multi-step import flow. With siblings named mnemon_import_cutover and mnemon_import_status present, the description should say whether this call must be followed by those, but it offers no when-to-use or ordering guidance.

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