Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_cleanup_storage

Destructive

Delete only explicitly supplied local-ydb storage paths or Docker volumes. Run without confirm=true to see the cleanup plan and remove nothing, then set confirm=true to apply the cleanup.

Instructions

Delete only the explicitly supplied local-ydb host paths or Docker volumes. Use after inspecting local_ydb_storage_leftovers; without confirm=true this returns the cleanup plan and removes nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsNoExplicit host filesystem paths to remove. Nothing is deleted unless each path is supplied here and confirm=true.
confirmNoMust be true to remove the explicitly supplied storage paths or Docker volumes. Omit or false for plan-only output.
profileNoNamed profile from local-ydb.config.json. Defaults to config.defaultProfile.
volumesNoExplicit Docker volume names to remove. Nothing is deleted unless each volume is supplied here and confirm=true.
configPathNoAbsolute path to an explicit local-ydb config file. Missing, unreadable, oversized, or invalid explicit files fail closed instead of using defaults.

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.12
  3. Removedv0.1.12
  4. Addedv0.1.5
  5. Removedv0.1.4
  6. Changed5 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."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to remove the explicitly supplied storage paths or Docker volumes. Omit or false for plan-only output."
    • addedInput schema / properties / paths / description
      Added value: +"Explicit host filesystem paths to remove. Nothing is deleted unless each path is supplied here and confirm=true."
    • addedInput schema / properties / profile / description
      Added value: +"Named profile from local-ydb.config.json. Defaults to config.defaultProfile."
    • addedInput schema / properties / volumes / description
      Added value: +"Explicit Docker volume names to remove. Nothing is deleted unless each volume is supplied here and confirm=true."
  7. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds a safety contract beyond that: nothing is removed unless paths/volumes are explicitly supplied AND confirm=true, and the default behavior is plan-only output. This materially changes how an agent should invoke the tool and matches the destructive annotation (no contradiction).

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 with zero waste: the first defines the action and scope, the second adds the sequencing and the critical safety gate. Every clause earns its place.

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?

For a destructive, multi-parameter tool with no output schema, the description fully defines the safe invocation envelope: what is deletable, the confirm requirement, the plan-only default, and the recommended preceding step. No critical information for correct invocation 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 coverage is 100% and each parameter already carries a detailed description, including the confirm gate and configPath fail-closed behavior. The description reinforces the cross-parameter contract (explicit supply + confirm) but adds little beyond what the schema already states, so the baseline 3 applies.

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?

States a specific verb and resource: 'Delete only the explicitly supplied local-ydb host paths or Docker volumes.' The strict scoping constraint and the contrast with the inspection sibling local_ydb_storage_leftovers distinguish it clearly from the other 38 sibling tools, especially the destructive destroy_stack.

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?

Gives explicit sequencing guidance ('Use after inspecting local_ydb_storage_leftovers') and states the confirm=true gating condition that controls plan-only vs. actual deletion. It does not enumerate when-not-to-use scenarios beyond the explicit-supply constraint, but the usage context is unambiguous.

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