Skip to main content
Glama

submit_spin_states_workflow

Calculate energies for different spin multiplicities of molecules to analyze transition metal complexes, radical species, and magnetic properties.

Instructions

Submit a spin states workflow to calculate energies of different spin multiplicities.

FORMATTING NOTES (for MCP Inspector):

  • initial_molecule: Plain SMILES string (e.g., CCO, O=O)

  • states: JSON array without outer quotes (e.g., [[0,1], [0,3]])

Args: initial_molecule: SMILES string representing the molecule states: JSON array of [charge, multiplicity] pairs to calculate Multiplicity = 2S + 1 where S is total spin - Singlet (S=0): multiplicity = 1 (paired electrons) - Doublet (S=1/2): multiplicity = 2 (one unpaired electron) - Triplet (S=1): multiplicity = 3 (two unpaired electrons) - Quartet (S=3/2): multiplicity = 4 (three unpaired electrons) - Quintet (S=2): multiplicity = 5 (four unpaired electrons) solvent: Solvent environment, name or SMILES (default: empty for gas phase) name: Workflow name for identification and tracking folder_uuid: UUID of folder to organize this workflow. Empty string uses default folder. max_credits: Maximum credits to spend on this calculation. 0 for no limit.

Spin state calculations are essential for understanding:

  • Transition metal complexes and coordination chemistry

  • Radical species and open-shell molecules

  • Magnetic properties and spin crossover

  • Reaction mechanisms involving spin forbidden transitions

Returns: Workflow object representing the submitted workflow

Examples (MCP Inspector format): # Compare singlet and triplet states for oxygen initial_molecule: O=O states: [[0,1], [0,3]] name: O2 spin states

# Ethanol singlet and triplet (simple test)
initial_molecule: CCO
states: [[0,1], [0,3]]
name: Ethanol spin states

# Methylene carbene singlet and triplet
initial_molecule: [CH2]
states: [[0,1], [0,3]]
name: Methylene spin states

# Iron complex with multiple spin states
initial_molecule: [Fe+2]
states: [[2,1], [2,3], [2,5]]
solvent: water
name: Fe2+ aqueous spin states

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initial_moleculeYesSMILES string of the molecule for spin state calculations
statesYesJSON array of [charge, multiplicity] pairs. Format: [[0,1], [0,3]] (no outer quotes)
solventNoSolvent environment for calculations (name or SMILES). Empty string for gas phase
nameNoWorkflow name for identification and trackingSpin States Workflow
folder_uuidNoUUID of folder to organize this workflow. Empty string uses default folder
max_creditsNoMaximum credits to spend on this calculation. 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. It discloses that this is a submission tool (implies mutation/creation), mentions resource constraints ('Maximum credits to spend'), and provides context about what gets calculated. However, it doesn't mention authentication needs, rate limits, or whether the workflow can be stopped/updated/deleted (though sibling tools suggest these exist).

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

Conciseness3/5

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

The description is appropriately front-loaded with the core purpose, but includes extensive examples and application contexts that, while helpful, make it longer than necessary. The formatting notes and examples section are valuable but could be more concise. Every sentence earns its place, but the structure could be tighter.

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?

Given 6 parameters, no annotations, and no output schema, the description does well by explaining the tool's purpose, providing parameter guidance, and giving examples. However, it doesn't fully describe the return value ('Workflow object representing the submitted workflow' is vague) or mention how to track/retrieve results using sibling tools like 'retrieve_workflow'.

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 baseline is 3. The description adds significant value by explaining the 'states' parameter in detail (defining multiplicity, providing spin state examples from singlet to quintet), and includes formatting notes that clarify how to structure the JSON array. This goes well beyond what the schema provides.

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 tool's purpose with specific verb ('submit') and resource ('spin states workflow'), and explains what it calculates ('energies of different spin multiplicities'). It distinguishes itself from sibling tools like 'submit_basic_calculation_workflow' by focusing specifically on spin state calculations.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('Spin state calculations are essential for understanding...') with specific applications listed. However, it doesn't explicitly state when NOT to use it or name alternatives among the sibling tools for different types of calculations.

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