Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

db_setup_remove

Undo a saved database profile: remove an instance's db_profile and optionally delete its stored password secret. Confirm with the user before running.

Instructions

Remove an instance's db_profile and its stored DB secret — the undo for db_setup_save. Mutating: confirm with the user first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoWebsite/app to remove when the instance hosts several DBs. Required if there is more than one.
instance_idYesInstance whose db_profile to remove.
delete_secretNoAlso delete the password from the secret store (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.24.0
  2. Removedv2.23.8
  3. Changed1 schema field changedv2.23.0
    • addedInput schema / properties / app
      Added value: +{
+  "default": "",
+  "description": "Website/app to remove when the instance hosts several DBs. Required if there is more than one.",
+  "type": "string"
+}
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is mutating (destructive) and affects both db_profile and secret. It does not detail error handling or idempotency, but the main behavioral traits are well communicated.

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?

Two sentences: the first explains purpose and relationship, the second gives a usage warning. Every word adds value, no fluff. The structure is clear and front-loaded.

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

Completeness4/5

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

Given the tool's simplicity (3 parameters, no output schema), the description covers the main aspects: what it does, its relation to a sibling, and a safety guideline. It does not explain return values or edge cases, but for a removal tool with a clear undo role, this is adequate. A minor addition about what happens if the instance doesn't exist could improve completeness.

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%, so parameters are already documented. The description adds context by framing the tool as the undo operation, which helps interpret the parameters (especially delete_secret). However, it does not provide per-parameter details beyond the schema, so the added value is moderate.

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 description clearly states the verb 'Remove', the resource 'db_profile and its stored DB secret', and explicitly names the sibling tool 'db_setup_save' as the undo operation. This distinguishes it from other tools in the sibling list and makes the purpose unambiguous.

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?

The description says 'the undo for db_setup_save' which tells when to use it. It also adds 'Mutating: confirm with the user first' as a guideline for safe use. It doesn't explicitly describe when not to use, but the sibling context makes the scope clear. A small gap is the lack of alternative tool references for non-undo scenarios.

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