Skip to main content
Glama

local_ydb_scheme

Read-onlyIdempotent

Lists or describes YDB database schema objects with configurable output options and capped response size.

Instructions

Read-only YDB scheme list or describe with capped stdout/stderr. It uses the root database for rootDatabase paths and the tenant database otherwise; list supports recursive/long/onePerLine flags, describe supports stats, and incompatible flag combinations are rejected.

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.
actionNoScheme operation to run. Defaults to list.
pathNoScheme path to inspect. Defaults to the configured tenant root.
recursiveNoFor action=list, pass -R to recursively list subdirectories.
longNoFor action=list, pass -l for detailed object attributes.
onePerLineNoFor action=list, pass -1 to print one object per line.
statsNoFor action=describe, pass --stats.
maxOutputBytesNoMaximum UTF-8 bytes returned per stdout/stderr stream. Defaults to 65536.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by noting output capping, rejection of incompatible flag combinations, and the root-vs-tenant database routing, which are behavioral details beyond 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?

The description is concise (two sentences) and front-loaded with the core purpose. Every sentence adds useful information without redundancy or unnecessary length.

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 the tool's complexity (9 parameters, conditional flags, no output schema), the description covers key aspects: read-only nature, database selection, flag options, error handling, and output limitations. It is complete for a read-only inspection tool.

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?

The input schema has 100% description coverage, so baseline is 3. The description summarizes the parameter roles but adds no new meaning beyond what the schema already provides for each parameter.

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 it's a read-only tool for listing or describing YDB schemes, distinguishing it from sibling tools that write or modify schemas (e.g., local_ydb_apply_schema). It mentions database selection and specific flags, making the action precise.

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 provides context on when to use the tool (read-only scheme enumeration/inspection) and the database selection logic, but does not explicitly state when not to use it or suggest alternative tools for other operations.

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