Skip to main content
Glama

significant_figures

Round a number to a specified number of significant figures, with a default of 3, to control numerical precision in calculations.

Instructions

Round a number to a specified number of significant figures.

Parameters:
    value — Number to round.
    sig_figs — Number of significant figures (default: 3).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
sig_figsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It describes the basic rounding operation but does not detail edge cases (e.g., rounding zero, negative numbers) or tie-breaking rules. For a simple mathematical function, this is adequate but lacks comprehensive transparency.

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 extremely concise, consisting of a single introductory sentence followed by a parameter list. Every sentence is necessary and information-dense, with no wasted text.

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?

Given the presence of an output schema (not shown), the description does not need to explain return values. The tool is simple, and the description covers the core functionality. A minor omission is the lack of explicit rounding rule (e.g., standard rounding), but this is common knowledge for significant figures.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by clearly explaining each parameter: 'value — Number to round. sig_figs — Number of significant figures (default: 3).' This adds meaningful context beyond the schema's type and default information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Round a number to a specified number of significant figures.' It uses a specific verb ('Round') and a specific resource (number with significant figures), making the purpose unambiguous and distinct from sibling tools.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of when not to use it (e.g., for decimal place rounding) or comparison to related tools like scientific_notation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server