Skip to main content
Glama

Reset webspace database password

webspace_reset_db_password
Destructive

Reset the MariaDB password for a webspace's database. Returns the new plaintext password ONCE — store it immediately. Existing apps will lose DB access until reconfigured — requires confirm:true.

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>",
      "confirm": "<confirm>"
    },
    "name": "webspace_reset_db_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
confirmYesMust be true to confirm — live applications will lose DB access until their config is updated with the new password.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description adds the two facts that matter most: the new password is returned in plaintext exactly ONCE and is unrecoverable if not stored, and dependent applications break until reconfigured. That is genuine behavioral value beyond the structured fields.

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?

Three short sentences, each carrying a distinct load: what it does, the one-time return value, and the blast radius. The most urgent fact (store the password immediately) is front-loaded.

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?

With no output schema, the description must explain the return value, and it does so decisively — a one-time plaintext password. Combined with the destructive-impact warning and the confirm requirement, an agent has everything needed to call this safely.

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 100%, and the `confirm` parameter's own description already spells out the live-application impact, so the description's mention of confirm:true largely restates the schema. The `id` format constraint is not discussed, but the schema covers it fully.

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 opens with a specific verb and resource: 'Reset the MariaDB password for a webspace's database.' That is clearly distinct in substance from the VPS password siblings, but no sibling is named, so the differentiation is left implicit rather than explicit.

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 gives clear situational context — existing apps will lose DB access until reconfigured, and confirm:true is mandatory — which tells the agent this is a deliberate, high-impact operation. It stops short of naming when to prefer an alternative (e.g., a VPS-level password tool) or any prerequisite checks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.