Skip to main content
Glama

Stoichiometry

stoichiometry
Read-only

Convert grams, moles, and particles, using a chemical formula when grams are involved, to support chemistry calculations and homework checks.

Instructions

Convert between grams, moles and particles. The formula is required whenever grams are the from or to unit. Converting between moles and particles needs no formula.

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": {
      "value": "<value>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "stoichiometry"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesWhat to convert it to.
fromYesWhat the value is in.
valueYesThe amount to convert.
formulaNoThe chemical formula, like H2O. Required when from or to is grams. Not used otherwise.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds essentially nothing beyond a restatement of the schema's formula requirement — no statement about numeric precision, significant figures, unit errors, or failure behavior for invalid formulas, which are the real behavioral concerns for a converter that has sibling round_sig_figs.

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?

Two sentences, no filler, with the core capability stated first and the single conditional constraint second. Nothing in it could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and the input contract is fully covered by schema plus description. The only meaningful omission is precision/rounding behavior, which matters given the round_sig_figs sibling but is not required to invoke the tool correctly.

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% and the schema itself already states 'Required when from or to is grams. Not used otherwise' for formula, so the description's formula rule is largely duplicative. With enums documented on from/to and the schema carrying the semantics, a baseline 3 is appropriate, though the description adds no numeric-range or precision hints.

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?

Names a specific operation (convert) over a specific domain of units (grams, moles, particles), so the agent knows exactly what the tool computes. It does not explicitly contrast with siblings like convert_units or molar_mass, but the stoichiometry framing is distinctive enough to route correctly in most cases.

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 description gives a usable conditional rule ('formula is required whenever grams are the from or to unit'), which tells the agent how to call the tool in the graded cases, but it is parameter-level guidance rather than tool-selection guidance. It never says when to prefer this over convert_units, molar_mass, or round_sig_figs, so the choice between siblings is left to inference.

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