Skip to main content
Glama

local_ydb_apply_schema

Destructive

Validates and applies YDB table DDL (YQL) using the official SDK. Action 'apply' requires explicit confirmation to execute after validation.

Instructions

Validate or apply YDB table DDL through the official YDB JS SDK. It accepts raw YQL DDL for PRAGMA plus CREATE TABLE, ALTER TABLE, and DROP TABLE; action=apply validates first and executes only with 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.
actionNoSchema operation to run. validate only checks the YQL DDL through the YDB SDK; apply validates first and executes only with confirm=true.
databasePathNoYDB database path for SDK validation/application. Defaults to the configured tenant root; root database paths use the static gRPC port.
scriptYesYQL DDL script to validate or apply. Supports PRAGMA plus CREATE TABLE, ALTER TABLE, and DROP TABLE statements.
confirmNoMust be true to execute action=apply after SDK validation succeeds. Omit or false for validation plus plan-only output.
timeoutMsNoSDK operation timeout in milliseconds. Defaults to 120000.
maxOutputBytesNoMaximum UTF-8 bytes returned per validation/execution issue stream. Defaults to 65536.
Behavior5/5

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

The description adds significant behavioral detail beyond annotations: it explains the validation-then-apply safety mechanism, the requirement of confirm=true for execution, and the supported DDL types (PRAGMA, CREATE/ALTER/DROP TABLE). This matches the destructiveHint=true and idempotentHint=false annotations without 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?

The description is two sentences, front-loaded with the core purpose, and every sentence adds essential information. There is no redundancy or fluff.

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?

The description covers the core purpose and key behavioral traits (validation-then-apply). However, it does not describe return values or error behavior, which is a gap given no output schema. The parameters for profiles and config paths are not contextualized, but the schema covers them. Overall, it is sufficient but not fully complete for a tool with 8 parameters.

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?

With 100% schema description coverage, the description adds minimal new meaning beyond parameter descriptions. It restates the action/confirm behavior already in the schema, but does not explain profile, configPath, or other parameters further. The description meets the baseline but does not enhance parameter understanding.

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 clearly states the tool validates or applies YDB table DDL, specifying the verb (validate/apply) and resource (YQL DDL for CREATE/ALTER/DROP TABLE). This distinguishes it from sibling tools like local_ydb_generate_schema, which generates schema, and local_ydb_scheme, which lists schema.

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 description implies usage for schema DDL operations and explains the two-step process (validate then apply with confirm). However, it does not explicitly mention when not to use it or provide alternatives among siblings, leaving some ambiguity for the agent.

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