Skip to main content
Glama

local_ydb_permissions

Destructive

List and modify YDB scheme permissions for a path. Supports grant, revoke, set, clear, chown, and inheritance changes with plan-first safety for mutations.

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
profileNoNamed profile from local-ydb.config.json. Defaults to config.defaultProfile.
configPathNoExplicit local-ydb config file path to load for this tool call. Useful when the MCP server should pick up a different config without restart.
actionNoPermissions operation to run. Defaults to list, which is read-only and does not require confirm.
pathNoScheme path to manage. Defaults to the configured tenant root.
subjectNoUser or group subject for grant, revoke, and set actions.
permissionsNoPermission names for grant, revoke, and set actions. Each item is passed as its own -p argument.
ownerNoNew owner for action=chown.
maxOutputBytesNoFor action=list, maximum UTF-8 bytes returned per stdout/stderr stream. Defaults to 65536.
confirmNoMust be true to execute mutating actions. Omit or false for plan-only output. Not required for action=list.
Behavior4/5

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

Annotations already show destructiveHint=true and readOnlyHint=false. Description adds value by explaining the plan/confirm workflow and that list is read-only. 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 sentences efficiently convey purpose and key behavioral nuance (plan vs execution). No unnecessary words.

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?

Given 9 parameters with full schema descriptions and no output schema, the description covers the essential workflow. Could optionally mention return format of plans, but adequate for understanding.

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 detailed parameter descriptions. The description does not add new parameter-level information beyond what is in the schema, so baseline score 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?

Description clearly states the tool inspects or changes YDB scheme permissions, listing specific actions (list, grant, revoke, etc.) and distinguishes read-only from mutating operations. This differentiates it from sibling tools like local_ydb_scheme.

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?

Explicitly notes default list is read-only and mutating actions return a plan unless confirm=true. Provides clear context for when confirm is needed, though does not explicitly contrast with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astandrik/local-ydb-toolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server