Skip to main content
Glama
Sign In
MolTalk

MolTalk

by DomFico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

3D Conformer (viewer)

conformer_3d
Read-onlyIdempotent

Generates one calculated 3D conformer aligned to a molecule's flat 2D drawing, so you can rotate the structure in 3D to inspect its geometry.

Instructions

Viewer-only: one calculated 3D conformer aligned to the flat drawing, used to rotate the drawing in 3D.

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": "conformer_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
smilesYes
hydrogensNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond annotations: it is viewer-only, returns exactly one conformer, and the conformer is aligned to the flat drawing for 3D rotation. It does not cover rate limits or auth, but those are less critical for a read-only viewer tool.

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 a single front-loaded sentence that starts with the key scope constraint ('Viewer-only') and adds only relevant details about the conformer and its purpose. There is no redundant or wasteful wording.

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

Completeness3/5

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

Given the simple read-only viewer nature and the presence of an output schema, the description covers purpose and behavioral scope adequately. However, it is incomplete for the input parameters because neither 'smiles' nor 'hydrogens' is explained, and schema coverage is 0%.

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%, so the description must compensate for undocumented parameters. It does not explain the required 'smiles' parameter or the optional 'hydrogens' boolean at all, leaving the agent without guidance on what to pass or how 'hydrogens' affects the conformer.

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 identifies a specific resource: one calculated 3D conformer aligned to the flat drawing for viewer-only use. It distinguishes the tool from non-viewer siblings like analyze_molecule and export_structure through the 'Viewer-only' scope, though it does not explicitly state the verb (e.g., 'returns' or 'generates').

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?

The phrase 'Viewer-only' and 'used to rotate the drawing in 3D' imply when to use this tool rather than analysis or export siblings. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of alternatives, and no prerequisites or exclusions stated.

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

Deploy Server

Other Tools