Skip to main content
Glama

Lone Pair

Change an earlier figure

edit_drawing
Read-onlyIdempotent

Change a figure Lone Pair made earlier and get the new figure: add a structure to the right of it, change the journal style, or put a caption under it. Give the earlier result's drawing. Everything else in the drawing stays as it was. Moving or deleting atoms is not supported; draw the structure again instead. The result carries drawing (Lone Pair JSON to pass to edit_drawing or back in as input) and notes (anything changed on reading or lost in the format).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edit_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoA structure to add to the right of the drawing (SMILES, InChI, molfile).
dpiNoPNG resolution, 300 by default; 600 for print.
styleNoJournal style. acs = ACS Document 1996 (default), rsc = RSC, nature = Nature Reviews, slides = heavier lines for slides.
formatNopng (default; returned as an image), svg (returned as text), pdf or eps (returned as base64 in `data_base64`).
opaqueNoWhite background instead of transparent (SVG, PNG). Default false.
captionNoText to put under the drawing.
drawingNoThe `drawing` object from an earlier result.
add_is_nameNoTrue when `add` is a compound name to look up at PubChem. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With annotations already declaring read-only, idempotent, non-destructive behavior, the description adds that the original drawing is preserved and that the result carries `drawing` and `notes` for read-time changes or format loss. It could say more about error behavior or output modes, but the key behavioral caveats are disclosed.

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

Conciseness5/5

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

The description is front-loaded with the core operation, then constraints, then the return shape in four tight sentences. There is no filler or redundant restatement.

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 an eight-parameter editing tool without an output schema, the definition covers purpose, required input, unsupported edits, preservation semantics, and return fields. The annotations and fully described schema fill in the remaining structural details.

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 still adds useful meaning for `drawing` as the earlier result, `add` as a structure to the right, and the style/caption operations. It does not explain every parameter, but it improves how an agent selects and supplies the important ones.

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 states a specific operation: take an earlier drawing and return a changed version, with supported changes enumerated (add a structure to the right, change journal style, add a caption). It also clarifies the boundary by saying moving or deleting atoms is unsupported and directing the agent to redraw, which helps distinguish it from the draw sibling.

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?

It tells the agent to supply the earlier result's `drawing`, says everything else stays as it was, and gives a when-not case plus an alternative for structural edits. It does not explicitly compare against every sibling such as convert or render_reaction, but the intended use case and exclusions are clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources