Allen Brain API MCP Server

get_neuronal_models

Fetch biophysically detailed model records from Allen Institute APIs, with optional specimen filters and row limits.

Instructions

Fetch biophysically detailed model records (from BiophysicalApi/GlifApi).

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_neuronal_models"
  }
}

Input Schema

Name	Required	Description	Default
`specimenIds`	No	Filter by specimen IDs.
`numRows`	No	Maximum number of rows (default is 50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that it fetches records but does not disclose whether it is read-only, what happens when no parameters are given, if there are rate limits, or how pagination works (only the default of 50 rows is hinted by the schema). Significant gaps remain.

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 efficiently communicates the core purpose. It is front-loaded with the verb and resource, with no wasted words.

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 the tool has only two optional parameters, no output schema, and no annotations, the description provides a basic understanding. However, an agent may need more detail on what exactly constitutes a 'biophysically detailed model record' and how the response is structured. The description is adequate but not comprehensive.

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 no additional meaning beyond the schema for the parameters 'specimenIds' and 'numRows'. The source API name is mentioned but does not directly clarify parameter 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 states the verb 'Fetch', the resource 'biophysically detailed model records', and specifies the source 'BiophysicalApi/GlifApi'. This provides a specific and distinguishable purpose among sibling tools, which are mostly download and query tools for different 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 offers no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it. The agent is left to infer usage from the tool name and description alone.

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