ASTRA Unified Research Lab MCP Server

np_configure_stim

Define and upload charge-balanced biphasic stimulation parameters for NeuroPlatform, specifying electrode index, pulse timing, amplitudes, and polarity with automatic validation.

Instructions

NeuroPlatform v2 — Define, validate & upload a StimParam (charge-balanced biphasic stimulation)

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

Input Schema

Name	Required	Description	Default
`index`	No	Electrode index [0-127]
`enable`	No
`nb_pulse`	No	Number of pulses (0/1 = single)
`polarity`	No		NegativeFirst
`trigger_key`	No	Trigger key [0-15]
`phase_duration1`	No	D1 [µs]
`phase_duration2`	No	D2 [µs]
`phase_amplitude1`	No	A1 [µA]
`phase_amplitude2`	No	A2 [µA]
`pulse_train_period`	No	Pulse train period [µs]
`enforce_charge_balance`	No	Reject upload if phases are not charge-balanced

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Aug 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Define, validate & upload.' It does not mention side effects on hardware, permission requirements, reversibility, error behavior, or confirmation of successful upload, so the agent is left guessing about what actually happens.

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?

A single sentence that is concise, front-loaded with the action, and contains the key domain context. There is no wasted text.

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?

Despite a rich schema, the description is too sparse for an 11-parameter hardware-upload tool with no annotations and no output schema. It does not describe what the tool returns, how uploads are confirmed, failure modes, or prerequisites, so the agent would lack essential context for reliable invocation.

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 82%, so the parameters are mostly self-documenting with units, defaults, and ranges. The description adds the context of 'charge-balanced biphasic stimulation' but does not elaborate on how parameters interact or what 'validate' means for the charge-balance constraint.

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 uses a specific verb set ('Define, validate & upload') and names a concrete resource ('StimParam (charge-balanced biphasic stimulation)'), clearly distinguishing this hardware-configuration tool from siblings like np_send_trigger or np_count_spikes.

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 is provided on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description implies an upload/configuration action but does not explain when an agent should choose it over related np_* tools.

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

Deploy Server