Generate a spike raster figure for a selected time window (up to 60 seconds), shading unrecorded spans to clarify neural activity. Specify session, duration, and unit limits to visualize spiking patterns.
Figure: spike raster for a time window (max 60 s), with unrecorded spans shaded.
| Name | Required | Description | Default |
|---|---|---|---|
| t0 | No | ||
| max_units | No | ||
| duration_s | 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?
With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the 60-second limit and the shaded unrecorded spans, but it does not state whether the figure is displayed or returned, whether the session must be open, or any side effects such as writing files.
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?
The description is very short, front-loaded, and contains no filler or redundant phrasing. It earns its place with two concrete details, though it is arguably too sparse for the parameter coverage gap.
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 4-parameter plotting tool with no output schema and no annotations, the description omits parameter meanings, return/output behavior, and when to prefer this plot over sibling plotting tools. An agent would need to inspect the schema and other tools to use it confidently.
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?
Schema description coverage is 0%, so the description needed to explain what session_id, t0, duration_s, and max_units mean. It only implies a time window via 'max 60 s', offering essentially no parameter-level semantics.
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 clearly identifies a spike-raster figure for a time window and uniquely mentions that unrecorded spans are shaded, which distinguishes it from sibling plot tools like plot_psth or plot_decoding. It is specific about what is plotted, though it uses the noun 'Figure:' rather than an explicit verb.
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?
There is no guidance about when to use plot_raster instead of plot_psth, plot_decoding, plot_probe, or other plotting siblings. No prerequisites, session requirements, or alternative-selection criteria are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.