Skip to main content
Glama

Draw reaction step

draw_reaction_step
Read-onlyIdempotent

Draw one reaction or mechanism step as A + B → C with conditions over the arrow and optional atom highlights, so each step can be explained directly below.

Instructions

Show ONE reaction or mechanism step as a scheme 'A + B → C' (conditions over the arrow). When explaining a mechanism, go step by step: call this tool for step 1, then explain step 1 directly below it in 1–4 sentences, then call it for step 2, and so on. Never draw all steps first and explain them afterwards. A step may have 1–4 species per side. Small byproducts (H2O, H+) can go in the products or in conditions. Mark the reacting centres with highlights (e.g. the attacking atom in blue, the electrophilic carbon or the bond that breaks in red). Write charged atoms with their H explicitly ([NH+], [OH2+]); a bracket atom without H becomes a radical and the step is refused. The result reports imbalance and unusual species (methyl/primary cations, strong base in acid); if one reveals a mistake, fix the step and call again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reactants": "<reactants>",
      "products": "<products>"
    },
    "name": "draw_reaction_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNoStep title shown under the scheme, in the user's language (e.g. '第 1 步:形成亚胺鎓离子').
radicalNoTrue only for radical chemistry (homolysis, radical chain steps); allows species with unpaired electrons.
productsYes
reactantsYes
conditionsNoReagents/conditions written over the arrow, e.g. 'H⁺, −H₂O' or 'NaOH, H₂O, Δ'. Use Unicode sub/superscripts.
highlightsNoOptional coloured halos on the species of this step, each naming its species by side and 1-based index, e.g. [{"side": "reactants", "index": 1, "smarts": "C(=O)O", "color": "red"}, {"side": "reactants", "index": 2, "atoms": [1], "color": "blue"}] (the second needs [OH2:1] in that SMILES). Mark what reacts: the attacking atom, the electrophilic atom, the bond that breaks or forms.
reversibleNoTrue to draw an equilibrium arrow (⇌) instead of →.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, but the description adds real behavioral detail: bracket atoms lacking explicit H are treated as radicals and the step is refused, and results report imbalance and unusual species such as methyl cations or strong base in acid. This is meaningful validation-behavior disclosure beyond the annotations, though it does not spell out the full refusal surface (e.g. server-side check failures).

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?

Front-loaded with the core purpose, then workflow, then notation rules — a sensible order. It is dense and runs long, but nearly every sentence carries an actionable constraint (1–4 species per side, H notation, highlight conventions); only the ordering advice repeats itself slightly.

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

Completeness5/5

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

For a 7-parameter drawing tool with no output schema, the description covers the drawing conventions, the per-step interaction pattern, and what the result reports back (imbalance, unusual species). Nothing an agent needs in order to call it correctly is missing.

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?

With 71% schema coverage the baseline is 3, and the description adds genuine semantics: byproducts like H2O/H+ may live in products or in `conditions`, highlights should mark attacking atom / electrophilic carbon / breaking bond with colours, and radicals require explicit H notation. The `radical` flag itself is only implied, which keeps it from a 5.

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?

"Show ONE reaction or mechanism step as a scheme 'A + B → C'" gives a specific verb, resource, and scope, including the visual form produced. The emphasis on ONE step separates it from draw_molecule and check_mechanism without needing their schemas.

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?

Explicit sequencing rule: call for step 1, explain step 1 in 1–4 sentences, then call for step 2, and never draw all steps before explaining. It also gives a recovery path — if the imbalance warning reveals a mistake, fix the step and call again.

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