Skip to main content
Glama

science.bragg

Read-onlyIdempotent

Computes the missing wavelength, interplanar spacing, or Bragg angle θ from nλ = 2d sin θ using order and the other two values, with degree/radian input and high-precision decimal results.

Instructions

브래그 회절 조건 n*lambda = 2 d sin(theta)에서 파장, 면간격, 회절각 중 하나를 구한다. order는 양의 정수이고 wavelength, spacing, angle 중 정확히 하나를 생략하며 나머지는 Decimal 문자열이다. 파장과 면간격은 같은 길이 단위로 넣고, angle은 unit='deg'(기본) 또는 'rad'이며 브래그각 theta 기준이다(2theta 아님). mpmath 40자리 계산 후 유효숫자 20자리로 돌려주며 sin theta가 1을 넘는 조합은 오류다.

Input Schema

NameRequiredDescriptionDefault
unitNodeg
angleNo
orderYes
spacingNo
wavelengthNo

Output Schema

NameRequiredDescriptionDefault
unitNo
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
angleNo
traceYes계산 근거(tool, formula, inputs, steps, output)
spacingNo
wavelengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the readOnly/idempotent annotations: mpmath 40-digit internal precision, 20-significant-digit output, unit consistency requirement, and an explicit error case when sin(theta) exceeds 1.

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?

The formula is front-loaded and every sentence contributes necessary information about constraints, units, precision, or errors. It is dense but appropriately sized for a technical calculator, with little wasted text.

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 formula-based science tool with an output schema, the description supplies all the operational detail an agent needs: which parameters are required, how units work, precision behavior, and the invalid-domain error condition.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: it defines order, the exact-one-omitted rule across wavelength/spacing/angle, Decimal string types, unit='deg'/'rad' behavior, and clarifies that angle means theta rather than 2theta.

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?

States a specific verb and resource: solving for one of wavelength, spacing, or diffraction angle in the Bragg condition. The formula and the exactly-one-omitted constraint make the tool's scope unmistakable.

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?

Gives clear usage constraints: order is a positive integer, exactly one of wavelength/spacing/angle must be omitted, and the remaining values are Decimal strings. It also explains unit handling for angle, though it does not explicitly name alternative tools or when not to use this one.

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