Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_add_storage_groups

Increase storage capacity by adding storage groups to a tenant storage pool. Returns a plan for review, then applies changes with confirm=true and verifies updated NumGroups and metadata.

Instructions

Increase NumGroups for one tenant storage pool using the current ReadStoragePool definition. Without confirm=true this returns the DefineStoragePool plan, rollback, target pool, and target count; when the update succeeds it verifies NumGroups and tenant metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of storage groups to add. 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.
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.2/5.0
Behavior5/5

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

Annotations only declare this as mutating, non-idempotent, and non-destructive. The description adds substantial behavior beyond that: the dual-mode plan/execute behavior, the exact plan payload (DefineStoragePool plan, rollback, target pool, target count), and post-success verification of NumGroups and tenant metadata. 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?

Two dense sentences with no wasted words. The first sentence front-loads the operation and data source; the second covers both behavioral modes and post-update verification. 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?

For a mutating tool with no output schema, the description sufficiently covers what plan mode returns and what happens upon success. It omits failure-path behavior and prerequisites (e.g., tenant/pool must exist), but the 100%-covered schema and the disclosed verification step keep the gaps minor.

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 rich parameter descriptions including defaults, the 1-10 count range, and the fail-closed configPath behavior. The description marginally reinforces the confirm semantics by linking it to the plan output, but does not need to compensate for any schema gap, so the baseline of 3 holds.

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?

"Increase NumGroups for one tenant storage pool" states a specific verb and resource with precise scope. The directional verb "Increase" inherently distinguishes it from the sibling local_ydb_reduce_storage_groups, and "using the current ReadStoragePool definition" adds precision about the source of truth.

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 conveys a clear plan-first workflow — confirm=false returns the DefineStoragePool plan and rollback, while confirm=true executes — which is genuine invocation guidance. However, it never names alternatives or states when not to use this tool versus reduce_storage_groups or storage_placement, so routing is left to inference.

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