Allen Brain API MCP Server

get_mouse_connectivity_experiments

Retrieve experiments from the Mouse Brain Connectivity Atlas, returning up to a specified number of rows to analyze neuronal connectivity data.

Instructions

Retrieve experiments from the Mouse Brain Connectivity Atlas.

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

Input Schema

Name	Required	Description	Default
`numRows`	No	Maximum number of rows to return (default is 50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided. Description only says retrieve; no info on pagination, default ordering, or what happens for empty results. Minimal behavioral disclosure.

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 concise sentence, straight to the point. Front-loaded with verb and resource. Could benefit from minimal expansion.

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?

No output schema, no annotations, no description of return format or result structure. Incomplete for a data retrieval tool.

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 description for numRows. Description adds no extra semantic value beyond schema.

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?

Clearly states verb 'Retrieve', resource 'experiments', and domain 'Mouse Brain Connectivity Atlas'. Distinct from siblings which are download functions or other entity 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?

No guidance on when to use this vs siblings like get_cell_specimens or get_structures. Agent must infer from resource name.

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