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

dandi-query-server

by bendichter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

execute_sql

Run complex SELECT queries on the DANDI database to retrieve and analyze neuroscience data.

Instructions

Execute advanced SQL queries against the DANDI database

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": "execute_sql"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesSQL query to execute (SELECT statements only, max 10,000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'execute advanced SQL queries', which implies a read operation from the schema constraint (SELECT only) but does not explicitly state it is safe (no writes), nor discloses any rate limits, timeout, or result size behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words. However, the description is too brief and could include more crucial info without being lengthy.

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

Completeness2/5

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

For a tool with no output schema and one parameter, the description omits important context such as return format (e.g., list of rows), whether results are paginated, and any performance implications. Given the sibling set including validation and schema tools, the description is incomplete for an agent to fully understand usage.

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 the sql parameter description including key constraints (SELECT only, max 10,000 chars). The tool description adds 'advanced' but no further meaning. Baseline 3 is appropriate as description complements schema but doesn't add much beyond.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it executes advanced SQL queries against the DANDI database, with verb 'execute' and resource 'advanced SQL queries'. However, it does not differentiate from sibling tool 'validate_sql', which also deals with SQL queries.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like validate_sql, search_assets, or search_datasets. Doesn't mention that validate_sql should be used first to test queries, or that this tool is for complex queries beyond simple filters.

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