Summarize population firing rates for a session over a specified time range, defaulting to the whole session. Use it to assess neural activity levels from spike recordings.
Population firing-rate summary over a time range (defaults to the whole session).
| Name | Required | Description | Default |
|---|---|---|---|
| t0 | No | ||
| t1 | No | ||
| session_id | Yes |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the behavioral burden. It implies a read/compute operation but never states that it is non-mutating, what data it requires, or what happens with t1=null. It also omits side effects, performance considerations, and error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no redundant wording. It is concise, though brevity is achieved by omitting important details like output shape and parameter units.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description must be self-sufficient. 'Population firing-rate summary' does not tell an agent what the response contains, what units are used, or how the time range relates to session timestamps, leaving too much to guess.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate. It does clarify that t0/t1 form a time range and that the default is the whole session, but it leaves units unspecified, does not explain session_id, and never states how t1=null is interpreted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a get operation on population firing rates over a time range, which is reasonably distinct from siblings like get_psth and plot_psth. However, 'summary' is vague—it does not specify whether this returns mean firing rate, spike counts, or a rate across neurons over time bins.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only usage hint is that the time range defaults to the whole session, which implies t0/t1 are optional. There is no explicit statement of when to choose this tool over get_psth or list_dataset_files, nor any prerequisites such as prior spike sorting or session opening.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.