Skip to main content
Glama

start_streaming

Launch a parallel pipeline that processes each scan independently through cortical tiles, config, and embeddings stages, then combines results after all scans complete.

Instructions

Launch scan-centric streaming pipeline: one worker per scan runs stages 2-4 in parallel.

Each worker owns one ScanId and processes cortical_tiles → config → embeddings sequentially for its scan, using file-presence barriers between stages. Stage 5 (combine) runs once after all workers drain.

Requires embeddings_only mode (training aggregates all subjects and cannot be parallelised per-scan).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidsNo
datasetYes
dry_runNo
input_dirYes
n_workersNo
output_dirYes
short_nameNoeval
sk_qc_pathNo
models_pathNo
datasets_rootNo
path_to_graphYes
poll_intervalNo
worker_timeoutNo
embeddings_pathNochampollion_V1
path_sk_with_hullYes
dataset_localizationNolocal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes worker-per-scan processing, sequential stages, file-presence barriers, and post-processing combine stage. No annotations provided, so description fully covers behavioral traits.

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?

Highly concise with zero wasted sentences. Important information is front-loaded, and the structure efficiently conveys complex workflow.

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 good behavioral coverage, the tool has 16 parameters with no documentation and an output schema not described. For a complex pipeline tool, this is insufficient to guide invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 16 parameters, the description fails entirely to explain what each parameter does or how they relate to the pipeline behavior. Only mode constraint is mentioned implicitly.

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 it launches a scan-centric streaming pipeline with specific stages, distinguishing it from sibling tools that handle individual stages or other pipelines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly specifies when to use (embeddings_only mode) and when not (training mode cannot be parallelised), providing clear context over alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Barthelemy-Drabczuk/champollion_sulcal_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server