Skip to main content
Glama

batch_submit_workflow

Submit multiple molecules for parallel chemical property calculations like pKa, solubility, or descriptors using Rowan's computational chemistry platform.

Instructions

Submit multiple workflows of the same type for different molecules using Rowan v2 API.

FORMATTING NOTES (for MCP Inspector):

  • initial_molecules: Enter as JSON array without backslashes: ["CCO", "CCCO", "CCCCO"]

  • workflow_data: Enter as JSON object without backslashes: {"key": "value"}

  • names: Enter as comma-separated text OR JSON array: Phenol pKa, Acetic Acid pKa

Args: workflow_type: Type of workflow to run (e.g., pka, descriptors, solubility, redox_potential) initial_molecules: JSON array of SMILES strings to process in batch workflow_data: JSON object of workflow-specific parameters (default: empty for defaults) names: Comma-separated workflow names or JSON array (default: auto-generated) folder_uuid: UUID of folder to organize workflows. Empty string uses default folder. max_credits: Maximum credits to spend per workflow. 0 for no limit.

Processes multiple molecules through the same workflow type efficiently. Useful for:

  • High-throughput property prediction

  • Library screening

  • Dataset generation for machine learning

  • Systematic comparison of molecules

Supported workflow types include: 'pka', 'descriptors', 'solubility', 'redox_potential', 'conformer_search', 'tautomers', 'strain', 'ion_mobility', 'fukui', and more. Note: 'nmr' requires subscription upgrade and is not currently available.

Returns: List of Workflow objects representing the submitted workflows

Examples: # Batch pKa calculations (MCP Inspector format) workflow_type: pka initial_molecules: ["Oc1ccccc1", "CC(=O)O", "c1c[nH]cn1"] names: Phenol pKa, Acetic Acid pKa, Imidazole pKa

# Batch descriptor generation
workflow_type: descriptors
initial_molecules: ["CCO", "CCCO", "CCCCO", "CCCCCO"]
names: Ethanol, Propanol, Butanol, Pentanol

# Batch conformer search with custom settings
workflow_type: conformer_search
initial_molecules: ["CCOCC", "c1ccccc1C", "CC(C)C"]
workflow_data: {"conf_gen_mode": "rapid", "final_method": "aimnet2_wb97md3"}

# Batch solubility predictions
workflow_type: solubility
initial_molecules: ["CC(=O)Nc1ccc(O)cc1", "CN1C=NC2=C1C(=O)N(C(=O)N2C)C"]
workflow_data: {"solvents": ["water", "ethanol"], "temperatures": [298.15, 310.15]}

Time varies based on workflow type and number of molecules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_typeYesType of workflow to run in batch (e.g., pka, descriptors, solubility, conformer_search)
initial_moleculesYesJSON array of SMILES strings. Format: ["CCO", "CCCO", "CCCCO"] (no backslashes or outer quotes)
workflow_dataNoJSON object of workflow-specific parameters. Format: {"key": "value"} or empty for defaults
namesNoComma-separated workflow names OR JSON array. Format: Phenol pKa, Acetic Acid pKa OR ["Name 1", "Name 2"]. Auto-generated if empty
folder_uuidNoUUID of folder to organize these workflows. Empty string uses default folder
max_creditsNoMaximum credits to spend per workflow. 0 for no limit
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it mentions credit limits ('max_credits'), time variability based on workflow type and molecule count, and subscription requirements for certain workflow types ('nmr requires subscription upgrade'). However, it doesn't explicitly state whether this is a read-only or mutation operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (formatting notes, args, usage contexts, supported types, returns, examples). While comprehensive, some information like the extensive examples could be considered slightly verbose, though each example serves a distinct illustrative purpose for different workflow types.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with no annotations and no output schema, the description provides excellent coverage: purpose, usage guidelines, parameter formatting, behavioral constraints, return values, and multiple examples. The main gap is lack of explicit safety/authorization information, but otherwise it's nearly complete for agent understanding.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema by providing formatting notes with concrete examples, explaining what 'auto-generated' means for names, clarifying that empty strings use defaults, and listing supported workflow types with availability notes. This compensates well for the schema's technical descriptions.

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 the specific action ('Submit multiple workflows of the same type for different molecules') and distinguishes it from sibling tools by emphasizing batch processing efficiency. It explicitly mentions using the Rowan v2 API, which provides technical context not present in the tool name alone.

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?

The description provides explicit usage contexts with a 'Useful for:' section listing four specific scenarios (high-throughput property prediction, library screening, dataset generation, systematic comparison). It also distinguishes this tool from single-workflow submission siblings by emphasizing batch efficiency for multiple molecules.

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/k-yenko/rowan-mcp'

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