Skip to main content
Glama

Balance equation

balance_equation
Read-only

Balance chemical equations written with -> and + by automatically determining the correct stoichiometric coefficients for reactants and products.

Instructions

Balance a chemical equation written with -> and +.

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": {
      "equation": "<equation>"
    },
    "name": "balance_equation"
  }
}

Input Schema

NameRequiredDescriptionDefault
equationYesEquation like H2 + O2 -> H2O

Output Schema

NameRequiredDescriptionDefault
balancedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the accepted input notation and says nothing about error behavior for invalid or unbondable equations. With annotations carrying the main burden this is acceptable but thin.

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, front-loaded with the verb and resource, with no filler. It is efficient, though the brevity is part of why the usage and edge-case guidance is missing.

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 annotations cover the read-only nature. For a one-parameter tool this is nearly sufficient; only the failure mode for malformed or impossible equations is unaddressed.

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?

There is a single parameter with 100% schema description coverage; the schema example already shows 'H2 + O2 -> H2O'. The description's 'written with -> and +' largely restates that example, adding no new constraints such as state symbols, charges, or whitespace handling.

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?

States a specific verb and resource ('Balance a chemical equation') plus the required notation ('->' and '+'), so the operation is unambiguous. It does not, however, distinguish itself from the sibling 'stoichiometry', which an agent could plausibly reach for the same input.

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?

Use is implied by the verb and by the notation constraint, but the description never says when to pick this over stoichiometry, nor any exclusion (e.g. already-balanced inputs, invalid formulas). Nothing explicit is offered beyond the format requirement.

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