Skip to main content
Glama
Sign In

Scientific Calculator

by ai.saifs
OverviewDiscussionsAdmin

Work Calculator

calculator_physics_work
Read-only

W = F × d × cos(θ). Angle optional (degrees); default 0°.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "force": "<force>",
      "displacement": "<displacement>"
    },
    "name": "calculator_physics_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNoAngle between F and d in degrees (default 0).
forceYesForce in Newtons.
displacementYesDisplacement in meters.

Output Schema

NameRequiredDescriptionDefault
resultYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 adds the formula and angle default, which is useful context but not behavioral disclosure beyond structured fields.

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 compact sentences with the formula front-loaded and the angle caveat immediately after. There is no wasted text.

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

Completeness4/5

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

For a simple calculator with a complete schema, output schema, and clear annotations, the description is sufficient to invoke it correctly. It could be improved by distinguishing this work calculation from nearby energy and physics calculators.

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 all parameters are already documented in the schema. The description repeats that angle is optional, in degrees, and defaults to 0°, adding no meaning beyond the schema.

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 formula 'W = F × d × cos(θ)' makes it clear this computes mechanical work from force, displacement, and angle. However, it never explicitly states a verb or differentiates itself from siblings like calculator_energy, calculator_potential_energy, or calculator_kinetic_energy.

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 guidance on when to use this work calculator versus related energy or force calculators. The description only gives the formula and default angle, leaving the agent to infer appropriate usage.

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