Allen Brain API MCP Server

get_grid_data_download_url

Retrieve a downloadable URL for 3-D expression grid data from a section data set, specifying energy, density, or intensity.

Instructions

Returns the URL to download 3-D expression grid data for a section data set (does not download).

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": {
      "sectionDataSetId": "<sectionDataSetId>"
    },
    "name": "get_grid_data_download_url"
  }
}

Input Schema

Name	Required	Description	Default
`sectionDataSetId`	Yes	Section Data Set ID.
`include`	No	What to include: 'energy' (default), 'density', or 'intensity'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the key behavioral trait 'does not download', but lacks details about URL lifetime, authentication, 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?

Single sentence efficiently conveys the core action, no unnecessary words, front-loaded with key information.

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

Completeness4/5

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

For a simple tool with two documented parameters and no output schema, the description adequately covers the return type and resource, though it could mention URL properties.

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 description coverage is 100% so baseline is 3. The description adds only the context '3-D expression grid data' but does not enhance parameter meaning beyond what the schema 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 returns a URL for 3-D expression grid data and explicitly says it does not download the data, distinguishing it from download siblings.

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 implies usage by contrasting 'returns URL' with 'does not download', but provides no explicit when-to-use or when-not-to-use guidance, nor names alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.