Skip to main content
Glama

Render structure SVG

render_structure_svg
Read-onlyIdempotent

Fetches a 2D chemical structure drawing as SVG when the host did not deliver it in the tool result, using a SMILES string and optional highlight options.

Instructions

Card-internal: fetch a drawing when the host did not deliver it in the tool result's _meta.

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>"
    },
    "name": "render_structure_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
smilesYes
highlightNo

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 the useful fact that this is a card-internal fallback renderer, but says nothing about the returned SVG or how the output is delivered.

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?

One short sentence with the fallback condition front-loaded and no filler. It is arguably too terse rather than padded, so it does not waste any words.

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?

There is no output schema, so the description would need to explain what the returned drawing looks like, and it does not. Combined with undocumented parameters (including a nested highlight object) for a rendering tool, the definition omits information an agent needs to call it 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% and the description mentions neither the required smiles parameter nor the nested highlight object. With two parameters, one of them a free-form nested object with additionalProperties, the description provides no meaning beyond bare parameter names.

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

Purpose3/5

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

"Fetch a drawing" names a verb and an output artifact, but never states that it renders an SVG from a SMILES structure, so the resource is left implicit. The sibling name draw_molecule plausibly overlaps, and the description does nothing to distinguish this fallback renderer from it.

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 gives a concrete triggering condition: call this only when the host did not deliver the drawing in the tool result's _meta. That is a clear context for use with an implied exclusion, but no alternatives are named and an agent cannot easily verify the _meta precondition from the text alone.

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