Skip to main content
Glama
astandrik

Local YDB MCP

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

local_ydb_inventory

Read-onlyIdempotent

Retrieve Docker inventory for a local-ydb profile; containers, volumes, and inspect data appear only when Docker is reachable. Failures return ok=false with reason, avoiding false empty-host results.

Instructions

Read-only Docker inventory for a local-ydb target profile. Success returns ok=true, Docker CLI/daemon state, containers, volumes, and inspect data for configured containers that actually exist; Docker CLI, daemon, or inventory failures return ok=false with a reason and omit inventory arrays so failure cannot be mistaken for an empty host. SSH target or probe failures use docker-inventory-failed with conservative Docker availability flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoNamed profile from local-ydb.config.json. Defaults to config.defaultProfile.
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.12
  3. Removedv0.1.12
  4. Addedv0.1.9
  5. Removedv0.1.8
  6. Addedv0.1.5
  7. Removedv0.1.4
  8. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description goes beyond them by explaining the success response shape (ok=true plus inventory arrays) and the failure response shape (ok=false with reason and omitting arrays), which prevents the agent from mistaking failure for an empty host. It also discloses that failures use docker-inventory-failed with conservative availability flags, a useful behavioral nuance not present in 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 compact yet information-dense: a single paragraph that front-loads the purpose, then covers success/failure semantics, and ends with SSH/probe failure routing. Every sentence adds value, and claims are precise rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only inventory tool with 2 optional fully-documented parameters, no output schema, and rich annotations, the description covers what an agent needs to know: purpose, success/failure shape, and availability-flag behavior. There is no obvious missing context that would cause an agent to invoke it incorrectly.

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%, so the schema already documents both parameters. The description adds some context around configPath ('Missing, unreadable, oversized, or invalid explicit files fail closed instead of using defaults') and profile defaults, but it doesn't need to do much more since both parameters are fully described in the schema.

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 states a specific verb+resource: read-only Docker inventory for a local-ydb target profile, and differentiates from siblings by scoping to Docker CLI/daemon state, containers, volumes, and inspect data. The failure semantics are clearly distinguished, so an agent can tell this apart from status-report or healthcheck tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly describes the conditions under which it is appropriate: local-ydb target profile, read-only inventory, with SSH target or probe failures routed to docker-inventory-failed with conservative availability flags. It does not name a direct alternative, but the scope is concrete enough that an agent would not confuse it with the listed siblings.

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