dandi-query-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_datasetsC | Search DANDI datasets using basic filters |
| search_assetsB | Search DANDI assets (files/sessions) using basic filters |
| execute_sqlC | Execute advanced SQL queries against the DANDI database |
| validate_sqlA | Validate SQL query without executing it |
| get_schemaC | Get database schema information |
| get_filter_optionsA | Get available filter options for basic search |
| get_full_schemaA | Get complete database schema with all tables and their columns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Basic Search Guide | Guide to using the basic search functionality with filters |
| SQL Query Guide | Guide to writing advanced SQL queries with examples |
| Database Schema Reference | Complete reference of available tables and fields |
| Basic Search Examples | Collection of example basic search queries |
| SQL Query Examples | Collection of example SQL queries for common use cases |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but `get_schema` and `get_full_schema` overlap significantly. The descriptions differ in wording but not in clear behavioral distinction, which could confuse an agent.
All tool names follow a consistent `verb_noun` pattern (e.g., `execute_sql`, `search_datasets`). Even `get_full_schema` adheres to this pattern with an adjective inserted. No mixing of conventions.
Seven tools cover querying, schema exploration, and validation. This is a well-scoped set for a database query server—enough tools to be useful without overwhelming the user.
The tool set covers core query, schema, and search needs. Missing conveniences like direct single-resource lookup by ID, but SQL can compensate. Minor gap in not having a tool for retrieving specific dataset details without SQL.