Skip to main content
Glama
Sign In

Scientific Calculator

by ai.saifs
OverviewDiscussionsAdmin

Frequency Calculator

calculator_frequency
Read-only

f = v / λ (primary). Also solves related wave pairs.

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_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequencyNoFrequency in Hz (optional if solving for other).
wave_speedNoWave speed in m/s.
wavelengthNoWavelength in meters.

Output Schema

NameRequiredDescriptionDefault
resultYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered and the description owes only computational behavior. It gives the primary formula but says nothing about how the tool behaves when multiple inputs are supplied, when none are supplied (all params optional), or what units/rounding are applied. 'Also solves related wave pairs' hints at reverse solving without disclosing the rules.

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?

Two short sentences, formula front-loaded, no filler. The second sentence is underwhelming but not wasteful in length.

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?

Output schema exists, so return values needn't be explained, and annotations cover safety. However, with zero required parameters and three all-optional inputs, the description should say how the tool decides what to solve for and which wave pairs are supported; that ambiguity is the main thing an agent needs and it is missing.

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% with units and examples for all three parameters, so the schema carries parameter meaning. The description's formula adds the relationship f = v/λ that ties the parameters together, which is modest added value; baseline 3 applies.

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

Purpose3/5

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

The formula f = v / λ names the resource (frequency) and the inputs implicitly, so the core purpose is inferable. But it never says plainly 'computes frequency from wave speed and wavelength', and 'also solves related wave pairs' is too vague to tell an agent what the reverse modes actually are, especially given siblings calculator_wavelength and calculator_speed.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool rather than calculator_wavelength, calculator_speed, or any of the ~120 sibling calculators. The only routing signal is the formula itself, which an agent must reverse-engineer into a use case.

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

All Scientific Calculator toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources