Reassign ownership of a PostgreSQL database to another user within the same account. Provide the database name and the target username.
Change a database's owning user (both must already belong to this account).
| Name | Required | Description | Default |
|---|---|---|---|
| db_name | Yes | ||
| db_username | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the behavioral burden. It clearly identifies a mutating action and a key precondition, but does not disclose side effects on the previous owner, error behavior, or whether the operation affects privileges.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. Every word contributes to understanding the operation and its precondition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter mutation with no output schema, the description covers the operation and the critical precondition. It does not describe return values or error cases, but those are less critical given the tool's low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only provides string type with no descriptions. The description adds meaning by clarifying that db_username is the new owning user and that both db_name and db_username must be existing resources within the account.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: changing a database's owning user. This clearly distinguishes it from sibling PostgreSQL tools like ecp_postgres_create_database, ecp_postgres_create_database_user, and ecp_postgres_grant_privileges.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly name alternatives or say 'use this when...', but the parenthetical requirement that both database and user already belong to the account implies this is not for creating resources. Usage context is present but implicit rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.