Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_reduce_storage_groups

Destructive

Reduce a tenant's storage groups by dumping, rebuilding the profile with a smaller storagePoolCount, restoring data, and reapplying auth, preserving dynamic node ports and aborting on incomplete definitions.

Instructions

Reduce NumGroups for a tenant storage pool by dumping the tenant, rebuilding the profile stack with a smaller storagePoolCount, restoring the dump, and reapplying auth when needed. Before dump or destroy, it inspects every one-off dynamic node and preserves its exact gRPC, monitoring, and IC ports; an incomplete definition aborts the rebuild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of storage groups to remove from the current tenant pool. Defaults to 1.
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.
dumpNameNoOptional dump directory name under profile.dumpHostPath to preserve before rebuild.
poolNameNoExplicit storage pool name. Defaults to <tenantPath>:<storagePoolKind>.
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.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 mark destructiveHint=true and readOnly=false; the description adds the concrete destructive workflow: dump, rebuild profile stack with smaller storagePoolCount, restore dump, and reapply auth. It also discloses the pre-dump/destroy inspection of one-off dynamic nodes to preserve exact ports and the abort-on-incomplete-definition safety behavior. The auth detail is somewhat vague ('when needed'), so it is not a perfect 5.

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 dense sentences with the core operation front-loaded and important safety behavior in the second. No filler or repeated schema content; every clause adds operational information.

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?

For a destructive multi-step operation with no output schema, the description covers the workflow, auth follow-up, dynamic-node port preservation, and abort condition. It is slightly incomplete about when auth reapplies and does not explicitly state the plan-only/confirm execution model, but the schema covers confirm.

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% with meaningful descriptions for all six parameters, so the baseline is 3 and the description does not need to add parameter detail. The description mentions storagePoolCount and auth conceptually but does not clarify any specific parameter beyond what the schema already provides.

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 opens with a specific verb and resource: 'Reduce NumGroups for a tenant storage pool', and then explains the mechanism. It is clearly differentiated from the sibling local_ydb_add_storage_groups by direction (reduce vs add).

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 intended use is implied by the action 'reduce' rather than explicitly stated. It never names alternatives such as add_storage_groups or says when not to use it, and there is no explicit plan-only vs execute guidance in the description, though the schema covers confirm.

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