Skip to main content
Glama

Round sig figs

round_sig_figs
Read-only

Round numbers to a specified number of significant figures to ensure correct precision in chemistry and physics calculations.

Instructions

Round a number to a given number of significant figures.

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

Input Schema

NameRequiredDescriptionDefault
valueYesThe number to round.
sigFigsYesHow many significant figures to keep.

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. The description adds nothing about rounding behavior (e.g. half-up vs banker's rounding) or how edge cases like negative values or trailing zeros are handled, so it does not go beyond the structured data.

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?

A single front-loaded sentence with zero filler. Nothing is redundant with the title and every clause carries 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?

With an output schema present, the return value need not be explained, and both parameters are fully described in the schema. The only meaningful omission is the rounding mode, which could affect results for tie-breaking cases.

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 both parameters (value, sigFigs) are documented inline, including the exclusiveMinimum constraint on sigFigs. The description adds no extra meaning such as acceptable ranges or rounding rules beyond the schema, so 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 names a specific verb (round) and resource (a number) plus the target semantics (significant figures), which is unambiguous. It does not differentiate from the sibling tools (molar_mass, balance_equation, stoichiometry, convert_units), but those serve clearly different purposes, so confusion risk is low.

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?

Usage is only implied: an agent would use this when a value needs rounding to N significant figures. There is no explicit when/when-not guidance or reference to alternatives such as convert_units, which also produces numeric output that may need rounding.

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