Skip to main content
Glama

Lone Pair

Formula, masses and identifiers

analyze
Read-onlyIdempotent

For each structure in the input: molecular formula, molecular weight, exact (monoisotopic) mass, elemental analysis, SMILES, InChI and InChIKey. For a reaction: each structure's role and whether atoms and charge balance (each drawn structure counted once). Calculated from the structure, not looked up. NMR, pKa and mass-spectrum estimates are not part of this tool.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSet to true when `input` is a compound name (e.g. "aspirin") rather than a structure. The name is sent to PubChem to find the structure; this is the only network call the server makes. Default false.
inputNoThe structure as text: SMILES, reaction SMILES (reactants>agents>products), InChI, a molfile, RXN, SD file, CDXML, CML or Marvin text, or a Lone Pair drawing (the JSON from an earlier result, or the SVG text of an earlier figure).
as_writtenNoDraw atoms that have too many bonds instead of refusing the structure. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world access. The description adds genuinely non-redundant behavior: values are computed rather than retrieved, reactions are analyzed per-structure with each drawn structure counted once, and balance checks cover both atoms and charge. That goes beyond what annotations or schema convey without contradicting them.

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?

Three tight sentences with no filler; each one carries distinct information (outputs, reaction behavior, exclusions). The lead is output-oriented rather than action-oriented ('For each structure in the input: ...'), which slightly delays the statement of what the tool does, but nothing is wasted.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so by listing every result field, plus the reaction-specific results. Combined with a fully documented schema for inputs, an agent has enough to call it correctly; only failure behavior (unparseable structures, what as_written changes in the output) is left implicit.

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

Parameters3/5

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

Schema description coverage is 100%, including the important note that name=true triggers the sole PubChem network call and that input accepts a wide format list. The description itself says nothing about any of the three parameters, so it adds no meaning beyond the schema — the baseline 3 applies.

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 enumerates the exact computed outputs (formula, molecular weight, monoisotopic mass, elemental analysis, SMILES, InChI, InChIKey) and adds a distinct reaction mode (roles, atom/charge balance), which is far more specific than the title alone. It also draws a line against property-estimation tools ('NMR, pKa and mass-spectrum estimates are not part of this tool'), though it never names a sibling such as convert or render_reaction as the alternative.

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 negative scope statements ('calculated from the structure, not looked up' and the NMR/pKa/mass-spec exclusion) imply when this tool is the wrong choice, which is useful routing context. However, there is no explicit 'use X instead for Y' and no statement of when a caller should prefer convert or draw over analyze, so usage selection still requires inference.

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