Skip to main content
Glama
Sign In

Scientific Calculator

by ai.saifs
OverviewDiscussionsAdmin

Acceleration Calculator

calculator_physics_acceleration
Read-only

a = (final_velocity - initial_velocity) / time (m/s²).

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": {
      "initial_velocity": "<initial_velocity>",
      "final_velocity": "<final_velocity>",
      "time": "<time>"
    },
    "name": "calculator_physics_acceleration"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesTime in seconds (non-zero).
final_velocityYesFinal velocity v in m/s.
initial_velocityYesInitial velocity u in m/s.

Output Schema

NameRequiredDescriptionDefault
resultYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 documented. The description adds the output unit (m/s²) via the formula, which is modestly useful return context, but it does not elaborate on precision, error handling, or deterministic behavior beyond what is implied.

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?

One formula, zero waste, and the computation is immediately front-loaded. There is nothing extraneous to remove.

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 physics calculator with full schema parameter descriptions, an output schema, and annotations covering safety, the formula plus unit is largely sufficient. Minor omissions like rounding behavior are not critical given the output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is already described. The description's formula adds genuine semantic value by showing the exact relationship among the three parameters—subtract initial from final, divide by time—which the schema alone does not express.

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 gives the exact formula a = (final_velocity - initial_velocity) / time, which unambiguously identifies the computation as acceleration. It is specific enough to distinguish from siblings such as calculator_physics_speed or calculator_physics_force, though it never states 'calculates acceleration' in prose—the formula and title together carry the purpose.

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 when-to-use guidance, no mention of alternatives, and no exclusions. The formula implies the required inputs but does not tell an agent when this calculator is the right choice versus related physics tools like calculator_physics_speed.

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