Execute parameterized SQL queries on YDB by supplying JSON parameters to safely pass values and prevent SQL injection.
Run a parameterized SQL query with JSON parameters
| Name | Required | Description | Default |
|---|---|---|---|
| sql | Yes | ||
| params | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.4Input schema / properties / params / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "additionalProperties": true,
+ "type": "object"
+ }
+]Input schema / properties / params / typeRemoved value: -"string"Input schema / titlePrevious value: -"query_with_paramsArguments"New value: +"ydb_query_with_paramsArguments"Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "Annotations": {
+ "additionalProperties": true,
+ "properties": {
+ "audience": {
+ "anyOf": [
+ {
+ "items": {
+ "enum": [
+ "user",
+ "assistant"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Audience"
+ },
+ "priority": {
+ "anyOf": [
+ {
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Priority"
+ }
+ },
+ "title": "Annotations",
+ "type": "object"
+ },
+ "TextContent": {
+ "additionalProperties": true,
+ "description": "Text content for a message.",
+ "properties": {
+ "_meta": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Meta"
+ },
+ "annotations": {
+ "anyOf": [
+ {
+ "$ref": "#/$defs/Annotations"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "text": {
+ "title": "Text",
+ "type": "string"
+ },
+ "type": {
+ "const": "text",
+ "title": "Type",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "text"
+ ],
+ "title": "TextContent",
+ "type": "object"
+ }
+ },
+ "properties": {
+ "result": {
+ "items": {
+ "$ref": "#/$defs/TextContent"
+ },
+ "title": "Result",
+ "type": "array"
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "title": "ydb_query_with_paramsOutput",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It only mentions JSON parameters but does not state if the query is executed (read/write), any limits, security implications, or whether results are returned. The behavioral transparency is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one short sentence), which is efficient but underspecified. It earns its place by being clear but lacks sufficient detail for a tool with no annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of parameterized SQL, no annotations, and an output schema, the description is incomplete. It does not mention return values (despite output schema existing), expected parameter formats, or relationship to sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate. It mentions 'JSON parameters' but does not explain the 'sql' parameter or the expected format/structure of 'params'. The added meaning is minimal compared to what is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (run), resource (parameterized SQL query), and method (with JSON parameters). It distinguishes from siblings like ydb_query (likely non-parameterized) and ydb_explain_query_with_params (explain vs execute).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like ydb_query or ydb_explain_query_with_params. The description lacks any context about preferences, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ydb-platform/ydb-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server