Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_destroy_stack

Destructive

Delete a profile's Docker-based YDB stack: remove containers, network, storage, and tenant metadata, with optional host-path cleanup after confirmation.

Instructions

Remove tenant metadata, local-ydb containers, network, and storage for a profile, with optional host-path cleanup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to execute planned commands. Omit or false for plan-only output.
profileNoNamed profile from local-ydb.config.json. Defaults to config.defaultProfile.
configPathNoAbsolute path to an explicit local-ydb config file. Missing, unreadable, oversized, or invalid explicit files fail closed instead of using defaults.
removeDumpHostPathNoDelete profile.dumpHostPath. Defaults to false because it may be shared.
removeAuthArtifactsNoDelete explicit authConfigPath, dynamicNodeAuthTokenFile, and rootPasswordFile when configured. Defaults to false.
removeBindMountPathNoDelete profile.bindMountPath when the profile uses a bind mount. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.21
    • changedInput schema / properties / configPath / description
      Previous value: -"Explicit local-ydb config file path to load for this tool call. Useful when the MCP server should pick up a different config without restart."New value: +"Absolute path to an explicit local-ydb config file. Missing, unreadable, oversized, or invalid explicit files fail closed instead of using defaults."
    • addedInput schema / properties / configPath / minLength
      Added value: +1
  2. Addedv0.1.13
  3. Removedv0.1.12
  4. Addedv0.1.5
  5. Removedv0.1.4
  6. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / configPath / description
      Added value: +"Explicit local-ydb config file path to load for this tool call. Useful when the MCP server should pick up a different config without restart."
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to execute commands. Omit or false for plan-only output."New value: +"Must be true to execute planned commands. Omit or false for plan-only output."
    • addedInput schema / properties / profile / description
      Added value: +"Named profile from local-ydb.config.json. Defaults to config.defaultProfile."
  7. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already communicate destructiveness, and the description adds concrete blast radius: tenant metadata, containers, network, storage, plus optional host-path cleanup. This goes beyond the annotation flags by naming what gets destroyed. No contradiction with annotations.

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?

A single sentence with no filler. The primary action and affected resources are front-loaded, and the optional host-path cleanup is clearly separated at the end. Every clause earns its place.

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?

The description, combined with the fully documented input schema and destructive annotations, gives an agent enough context to understand what is removed and how the confirm flag gates execution. No output schema exists, so return-value documentation is not required. A brief mention of irreversibility could further help, but destructiveHint already covers that signal.

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 each parameter is already well documented (confirm gating, profile defaulting, config fail-closed behavior, and the three removal booleans). The description summarizes the tool's scope but does not add per-parameter meaning beyond the schema, so baseline 3 is appropriate.

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?

Description uses the specific verb 'Remove' and enumerates the exact resources affected: tenant metadata, local-ydb containers, network, storage, and optional host paths. This clearly distinguishes the tool from narrower siblings like cleanup_storage and remove_dynamic_nodes.

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?

The description implies full-profile teardown via 'Remove ... for a profile' and optional host-path cleanup, but it does not explicitly state when to prefer this over alternatives such as restart_stack or cleanup_storage. Usage context is inferable rather than directly stated.

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