Skip to main content
Glama
The-40-Thieves

codecalc

by The-40-Thieves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Physical Constants

physical_constants
Read-onlyIdempotent

Look up a physical constant by name, such as speed of light or Planck's constant, or list all 22 available constants with their values for quick reference.

Instructions

Look up a physical constant (speed_of_light, planck, avogadro, gravity, electron_mass, gas_constant, ...) or list all 22 with values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoConstant to look up, e.g. 'speed_of_light', 'planck', 'avogadro'; omit to list all 22

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / name / description
      Added value: +"Constant to look up, e.g. 'speed_of_light', 'planck', 'avogadro'; omit to list all 22"
  2. Changed1 schema field changedv0.11.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "physical_constantsDictOutput",
+  "type": "object"
+}
  3. Changed4 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / name / title
      Added value: +"Name"
    • addedInput schema / title
      Added value: +"physical_constantsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior. The description adds the return expectation by saying 'with values', and it doesn't hide any side effects or contradictions. With annotations present, the bar for additional transparency is reasonably met.

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 whole description is one rich, front-loaded sentence. It says the main action first, lists examples, and gives the alternate mode without any filler or redundant explanations.

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

Completeness5/5

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

For a one-parameter, read-only lookup with a fully documented parameter, clear annotations, and a known fixed set of constants, the description covers everything needed. The availability of an output schema further reduces the need to describe return values.

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?

The schema already provides 100% description coverage for the single parameter, including the key examples and the omit-to-list-all behavior. The description repeats examples but adds no substantive semantic value beyond the schema, matching the baseline for high coverage.

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 states a specific action ('Look up a physical constant') and resource, provides concrete examples, and explicitly adds the alternative behavior of listing all 22 constants with values. This clearly differentiates it from sibling tools like convert_units or list_units.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: pass a specific constant name for a lookup, or omit the name to get the full list of 22. It doesn't name alternatives explicitly, but no sibling appears to overlap with this domain, so the guidance is sufficient.

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

Deploy Server

Other Tools