Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_permissions

Destructive

Manage YDB scheme permissions for a path: list current access, or plan and confirm grants, revokes, ownership, and inheritance changes with read-only default.

Instructions

Inspect or change YDB scheme permissions for a path. The default list action is read-only; grant, revoke, set, clear, chown, and inheritance changes return a plan unless confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoScheme path to manage. Defaults to the configured tenant root.
ownerNoNew owner for action=chown.
actionNoPermissions operation to run. Defaults to list, which is read-only and does not require confirm.
confirmNoMust be true to execute mutating actions. Omit or false for plan-only output. Not required for action=list.
profileNoNamed profile from local-ydb.config.json. Defaults to config.defaultProfile.
subjectNoUser or group subject for grant, revoke, and set actions.
configPathNoAbsolute path to an explicit local-ydb config file. Missing, unreadable, oversized, or invalid explicit files fail closed instead of using defaults.
permissionsNoPermission names for grant, revoke, and set actions. Each item is passed as its own -p argument.
maxOutputBytesNoFor action=list, maximum UTF-8 bytes returned per stdout/stderr stream. Defaults to 65536.

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. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / configPath / description
      Previous value: -"Explicit local-ydb config file path to load for this tool call."New 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."
  7. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations flag destructiveHint and readOnlyHint, but the description adds the crucial gating behavior: default is read-only, and grant/revoke/set/clear/chown/inheritance changes are plan-only until confirm=true. This goes beyond the annotations and helps an agent understand the tool's safety model.

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 deliver purpose, default action, mutation types, and the confirm gate with zero filler. The most important operational constraint is front-loaded in the first sentence.

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 nine-parameter, multi-action tool with no output schema, the description covers purpose, default behavior, and the confirm requirement while the schema documents all parameters. The only mild gap is the unspecified content of a 'plan,' but that does not hinder correct tool selection or invocation.

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 every parameter has a meaningful description, including action enum semantics and confirm behavior. The description names some actions already present in the enum but adds no new parameter-level detail, so the baseline of 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?

The description opens with 'Inspect or change YDB scheme permissions for a path,' giving a specific verb pair, a clear resource, and path scope. It also separates the read-only default (list) from mutating actions, clearly distinguishing the tool's domain from scheme-wide or auth-focused siblings.

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 second sentence explains that mutating actions return a plan unless confirm=true, and that the default list action is read-only. This gives clear operational context, though it names no alternative tools or explicit when-not-to-use conditions; no other sibling targets permissions, so the guidance is sufficient.

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