Skip to main content
Glama

wavelength_convert

Read-onlyIdempotent

Convert wavelength to frequency or frequency to wavelength, and get photon energy plus the electromagnetic spectrum band for the result.

Instructions

Convert between wavelength and frequency. Returns energy and EM spectrum band.

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

Input Schema

NameRequiredDescriptionDefault
frequency_hzNoFrequency in hertz.
wavelength_mNoWavelength in meters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful output context by stating that the result includes energy and the EM spectrum band, though it does not disclose assumptions such as vacuum propagation or handling of zero/negative inputs.

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?

Two short sentences, both front-loaded and free of waste. The first sentence states the operation and the second adds the return information.

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?

The description compensates somewhat for the missing output schema by naming what is returned. However, with both input parameters optional, it does not clarify whether the caller should provide exactly one of frequency_hz or wavelength_m, which is an important invocation detail.

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 fully documents both parameters at 100% coverage. The description does not add parameter-level guidance beyond the schema, so baseline 3 is appropriate.

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 states a specific conversion: wavelength to frequency and vice versa, plus the returned energy and EM spectrum band. This is clearly more specific than a generic converter, but it does not explicitly distinguish itself from sibling conversion tools such as convert_length.

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 purpose implies usage cases, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. For a tool sitting among many convert_* siblings, it could be clearer about when this is the right converter.

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