Bot-Hosting.net

Rotate a database password

databases_rotatePassword

Destructive

Generate a new password for a database deployment and restart it to apply it. The old password stops working at once: every app connecting with it loses access until it is updated, so confirm with the user first. Returns the new password in full. A running database restarts in the background (restarting: true, up to 2 minutes): poll deployments.get until it is running again. A stopped one applies it on its next start.

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

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses the irreversible effect ('old password stops working at once'), the downstream impact on connected apps, the restart mechanism with its async signature ('restarting: true, up to 2 minutes') and the required follow-up ('poll deployments.get'). It also covers the edge case of a stopped deployment, which annotations cannot express.

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?

Four sentences, each load-bearing: purpose, risk warning, return value, and post-call behavior. The most important constraint (old password dies immediately) is front-loaded right after the purpose.

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?

There is no output schema, so the description correctly states what comes back ('the new password in full') and the asynchronous completion path via deployments.get. For a single-parameter destructive mutation, nothing an agent needs to call it safely 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 description coverage is 0% for the single required parameter 'id', so the description must carry the meaning. It implies the id identifies the target 'database deployment' but never states the identifier's format or origin, leaving a modest gap.

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?

The first sentence gives a specific verb and resource ('Generate a new password for a database deployment') plus the immediate consequence ('restart it to apply it'). No sibling tool in the catalog does password rotation, so an agent can route to it unambiguously.

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?

It states a hard precondition ('confirm with the user first') and explains the blast radius that motivates it, which is exactly the gating information an agent needs. It does not name a lighter-weight alternative, but the destructive nature leaves little ambiguity about when this applies.

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

All Bot-Hosting.net tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?