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

dandi-query-server

by bendichter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_assets

Search DANDI assets (files/sessions) by filtering on species, dataset ID, session type, and measured variables.

Instructions

Search DANDI assets (files/sessions) using basic filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 20, max: 100)
offsetNoNumber of results to skip for pagination
speciesNoFilter by species
dandiset_idNoFilter by specific dataset ID
session_typeNoFilter by session type
variable_measuredNoFilter by variables measured (e.g., ['ElectricalSeries'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states the basic purpose without mentioning rate limits, error handling, response format, 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?

The description is a single, concise sentence that clearly communicates the tool's purpose without unnecessary words.

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?

Given the absence of an output schema and annotations, the description lacks details on return values, pagination behavior beyond limit/offset, and potential side effects. It is minimally adequate.

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 all parameters having descriptions. The description adds no additional meaning beyond 'using basic filters', so it meets the baseline but does not enhance understanding.

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 verb 'search' and the resource 'DANDI assets' with clarification 'files/sessions'. It distinguishes from siblings like search_datasets and execute_sql by specifying 'basic filters'.

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 description mentions 'basic filters' but does not provide explicit guidance on when to use this tool versus alternatives such as search_datasets or execute_sql. No when-not-to-use criteria or prerequisites are given.

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