FastMCP 3.2 OpenBCI server - BrainFlow EEG/EMG acquisition, signal processing, and OSC/LSL export.
Critical gaps across all tools. Tool names lack action verbs (openbci_board, openbci_stream, openbci_signal, openbci_export, openbci_trigger, agentic_openbci_workflow, openbci_help). Descriptions are present but generic and lack WHEN/WHY guidance. Input schemas visible but severely underspecified: most parameters lack type constraints, enums, or validation rules. No output schemas documented. Parameters like 'operation' are free-form strings with no enum constraints, inviting hallucinated values. No error handling guidance. Tool 'agentic_openbci_workflow' accepts only a 'workflow' string with no schema clarity, appears inferred rather than explicitly registered. Missing parameter descriptions for critical fields (e.g., what values does 'operation' accept?). No pagination, no result limits documented. Baseline: 90% of A+ tools start with action verbs; 100% have param descriptions; 100% document return types. This server has ~0% compliance.
Agentic workflow orchestration for OpenBCI operations
OpenBCI board connection and management operations
Data export via BrainFlow streamers (file, OSC, multicast)
Help and documentation access for OpenBCI operations
Signal processing operations including band power analysis and filtering
EEG/EMG data streaming control and snapshot acquisition
Trigger rule management and OSC event firing
Tool names lack action verbs. All 7 tools use noun-only or generic names (openbci_board, openbci_stream, openbci_signal, openbci_export, openbci_trigger, agentic_openbci_workflow, openbci_help). LLMs cannot infer intent from names alone. Should be: connect_openbci_board, start_eeg_stream, analyze_signal_band_power, export_to_streamer, send_trigger_osc, execute_openbci_workflow, get_openbci_help.
Critical parameter 'operation' is free-form string with no enum constraint across all tools. openbci_board accepts 'connect, disconnect, status, list_ports, list_boards, probe' but no enum defined. openbci_stream accepts 'start, stop, snapshot, marker', no enum. LLMs will hallucinate invalid values like 'connect_wireless' or 'start_recording'. Must declare enums in schema.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. What does openbci_board return on 'status'? What fields? What does openbci_stream 'snapshot' return? Baseline: 100% of A+ tools document return types. Must add explicit output schema for each tool.
Parameter descriptions are missing or trivial. 'max_samples' in openbci_stream and openbci_signal lacks range/default. 'board_key' in openbci_board says 'Board identifier (e.g., cyton)', example values in descriptions cause LLMs to reuse them literally. Should be: 'board_key (string, enum: cyton, ganglion, brainbit, synthetic), the OpenBCI board model to connect'.
Tool 'agentic_openbci_workflow' accepts only 'workflow' string parameter with no schema clarity. Appears inferred rather than explicitly registered with full definition. Must provide explicit workflow enum or reference documentation.