Skip to main content
Glama

Describe selected atoms

describe_selection
Read-onlyIdempotent

Convert user-selected atoms and source SMILES into a fragment and atom-mapped SMILES for chemcard structure or reaction diagrams.

Instructions

Card-internal: turn atoms the user clicked into fragment and atom-mapped SMILES.

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": {
      "smiles": "<smiles>",
      "atoms": "<atoms>"
    },
    "name": "describe_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
atomsYes
smilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value by disclosing the two-part return (fragment SMILES and atom-mapped SMILES), which matters since there is no output schema, but it says nothing about invalid/empty atom lists or how the indices relate to the supplied SMILES.

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?

A single front-loaded sentence with the scoping qualifier first and no filler. It is efficient, though packing 'fragment and atom-mapped SMILES' into one clause leaves the dual output ambiguous rather than clear.

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?

For a tool with two required parameters, zero schema coverage, and no output schema, one sentence is thin. An agent still cannot tell which molecule the atom indices index into or what the returned strings look like, which are the details it would need to invoke and interpret results correctly.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description carries the full burden. 'Atoms the user clicked' gives a hint that the array holds atom references, but the relationship to the required 'smiles' string, the index base, and the expected ordering are all left unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete transformation: atom selections clicked by the user are converted into fragment SMILES plus atom-mapped SMILES. The 'Card-internal' prefix scopes it to an interactive UI context, which separates it in spirit from render_structure_svg and draw_molecule, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

'Card-internal' plus 'atoms the user clicked' implies the tool belongs to an interactive selection flow, so usage context is inferable. There is no explicit when-to-use/when-not guidance and no statement of what to call instead when the user has not made a selection.

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