Allen Brain API MCP Server

download_svg

Download a brain section image's SVG structure overlay to a local file. Filter by group label IDs for specific overlay types.

Instructions

Download SVG structure overlay for a section image to a local file.

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": {
      "sectionImageId": "<sectionImageId>"
    },
    "name": "download_svg"
  }
}

Input Schema

Name	Required	Description
`sectionImageId`	Yes	Section Image ID.
`filePath`	No	Local path to save the SVG (default: svg_{id}.svg).
`groups`	No	Optional group label IDs to filter which SVG types are returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It states a download operation (non-destructive) but does not disclose side effects, overwrite behavior, or permissions. This adds minimal behavioral context beyond the obvious.

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 sentence with no wasted words. It is front-loaded with the key action and resource.

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 no output schema and no annotations, the description could be more complete. It does not explain what the SVG overlay contains, how groups filter, or what happens on error. However, the schema covers parameters adequately.

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%, so the baseline is 3. The description does not add parameter-specific detail beyond what the schema already provides. It implies sectionImageId and filePath but no additional semantics.

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 specifies the action ('Download'), the resource ('SVG structure overlay for a section image'), and the destination ('to a local file'). It is specific and distinct from sibling tools that download other data types.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, filters, or contrast with sibling tools like download_section_image.

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