chemcard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHEMCARD_ALLOWED_HOSTS | No | Tunnel domain(s) to allow through the MCP SDK's DNS rebinding protection, e.g. xxxx.ngrok-free.app. Without it, requests return 421 Invalid Host header. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Whenever an answer is about a specific molecule or reaction (its structure, which part reacts, a mechanism), draw it inline like a textbook figure: draw_molecule for a molecule, draw_reaction_step for each step (check_mechanism first if multi-step). Interleave: figure, then its explanation. Mark the atoms/bonds you discuss with highlights. If the user selected atoms (mapped SMILES in their message), redraw from it and highlight them. Skip trivial species.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| draw_moleculeA | Show a clean 2D structure of ONE molecule inline in the explanation. Call it when the explanation refers to a specific molecule's structure (functional groups, protecting groups, stereochemistry, why it reacts as it does). Put each figure next to the paragraph about that molecule: when comparing two molecules, draw the first, explain it, then draw the second and explain it; do not draw both first. When the text is about part of the molecule (a group, an atom, a bond), highlight that part with |
| draw_reaction_stepA | 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 |
| render_structure_svgB | Card-internal: fetch a drawing when the host did not deliver it in the tool result's _meta. |
| describe_selectionB | Card-internal: turn atoms the user clicked into fragment and atom-mapped SMILES. |
| check_mechanismA | Validate a whole multi-step mechanism before drawing it (no figure is shown). Checks every species (valid SMILES, unexpected radicals from a bracket atom missing its H, unstabilised methyl/primary cations, strong bases under acidic conditions and vice versa, doubly charged species), each step's atom and charge balance, and that every step starts from an intermediate produced by the previous step. Call it once with all steps, fix every [error], consider each [warning], then draw the steps one at a time with draw_reaction_step. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ui://chemcard/card-v5.html |
TDQS
Scored across 5 tools
The tools mostly have distinct purposes: draw_molecule for single structures, draw_reaction_step for reaction schemes, check_mechanism for validation, and the two card-internal tools for rendering and selection parsing. The only mild overlap is between draw_molecule and render_structure_svg, but the latter is clearly marked as card-internal fallback behavior.
All names follow a consistent snake_case verb_noun pattern: draw_molecule, draw_reaction_step, render_structure_svg, describe_selection, check_mechanism. The minor format suffix in render_structure_svg does not break the overall convention.
Five tools is well-scoped for a chemistry explanation card assistant, and each tool has a clear, non-redundant role in drawing, validating, or handling user selections. No tool feels superfluous or missing from the core workflow.
The surface covers the main lifecycle: drawing single molecules, drawing reaction steps, validating multi-step mechanisms, and handling card-internal rendering and selections. A possible minor gap is lookup/conversion from compound names to SMILES, but that may be outside the stated visualization purpose.