Skip to main content
Glama

Scientific Constants

calculator_scientific_constants
Read-only

Look up CODATA/SI physical constants (c, G, h, e, NA, …).

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

Input Schema

NameRequiredDescriptionDefault
listNoList all constants.
queryNoConstant name/symbol/key.

Output Schema

NameRequiredDescriptionDefault
nameNo
valueNo
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes the data provenance (CODATA/SI), which helps trust the values, but says nothing about the list-vs-query interaction or the shape/size of results.

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; the resource and the source authority both appear immediately. Nothing could be cut without losing meaning.

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

Completeness3/5

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

With an output schema present and full schema coverage, the description doesn't need to explain return values. What it omits is disambiguation from a large sibling set containing two other constants tools, which is the one thing an agent still has to guess about.

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%, so 'list' and 'query' are already documented. The description's symbol examples (c, G, h, e, NA) loosely illustrate accepted query keys, but it doesn't clarify lookup tolerance (symbol vs full name vs key), which is where ambiguity actually lives.

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 ('look up') and a specific resource ('CODATA/SI physical constants') with concrete examples (c, G, h, e, NA). It does not differentiate itself from the closely related siblings calculator_math_constants and calculator_unit_constants, which is the main gap.

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?

There is no explicit when-to-use or when-not guidance and no named alternative. However, the parenthetical examples (G, h, NA, c) implicitly signal that this tool covers physics/CODATA constants rather than mathematical constants like pi, giving some inferable steering.

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.