Scientific Calculator

Speed Calculator

calculator_physics_speed

Read-only

Calculate speed v = distance / time (SI: m, s → m/s). Rejects zero time.

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": {
      "distance": "<distance>",
      "time": "<time>"
    },
    "name": "calculator_physics_speed"
  }
}

Input Schema

Name	Required	Description	Default
`time`	Yes	Time in seconds (non-zero).
`distance`	Yes	Distance in meters.

Output Schema

Name	Required	Description	Default
`unit`	No
`result`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context by disclosing the zero-time rejection rule, telling the agent a validation error is possible before it calls. It doesn't describe the response shape, but an output schema exists to cover that.

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 sentence plus a short constraint clause; the formula and units are front-loaded and nothing is padded or redundant.

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 two-parameter, closed-world read tool with full schema descriptions, annotations, and an output schema, the description covers what to expect including failure behavior. Only the response contents are unaddressed, and the output schema carries that.

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 both parameters are already documented with units and the non-zero constraint on time. The description's SI note restates rather than extends that, so baseline 3 applies.

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 plus the exact formula (v = distance / time) and the SI unit mapping (m, s → m/s). That formula cleanly separates it from siblings like calculator_physics_acceleration or calculator_physics_distance without needing their schemas.

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?

Usage is only implied by the formula: an agent can infer it applies when distance and time are known and speed is wanted. There is no explicit statement of when to prefer this over adjacent kinematics siblings, and no exclusions.

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

All Scientific Calculator tools Inspect

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.