Skip to main content
Glama
Sign In
dandi-query-server

dandi-query-server

by bendichter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

validate_sql

Checks SQL syntax and structure against the DANDI Archive schema to catch errors before execution, preventing costly mistakes in data queries without running the query.

Instructions

Validate SQL query without executing it

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sql": "<sql>"
    },
    "name": "validate_sql"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesSQL query to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only states that the tool validates without executing. It does not disclose what constitutes a validation outcome (e.g., syntax vs. semantic checks), error behavior, or any side effects.

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?

A single sentence that is front-loaded and conveys the essential information without any wasted words.

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

Completeness3/5

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

Given the simplicity of the tool (one parameter, no output schema), the description is adequate but lacks details on what the validation result includes (e.g., boolean, error messages), which would improve completeness.

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 one parameter 'sql' described as 'SQL query to validate'. The description adds no additional meaning beyond what the schema already provides.

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's action ('validate') and resource ('SQL query'), and explicitly contrasts with execution. This distinguishes it from the sibling 'execute_sql' tool.

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

Usage Guidelines3/5

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

The purpose implies use for validation rather than execution, but there is no explicit guidance on when to use this tool versus alternatives like 'execute_sql' or other validation methods.

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