Scientific Calculator

Force Calculator

calculator_physics_force

Read-only

Newton's second law F = m × a (Newtons).

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": {
      "mass": "<mass>",
      "acceleration": "<acceleration>"
    },
    "name": "calculator_physics_force"
  }
}

Input Schema

Name	Required	Description	Default
`mass`	Yes	Mass in kg.
`acceleration`	Yes	Acceleration in m/s².

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this as a read-only, non-destructive, closed-world calculation, so the safety profile is covered. The description adds the formula and output unit but does not add further behavioral details such as handling of negative or zero mass/acceleration.

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?

The definition is extremely concise and front-loads the formula and unit. It is efficient, though as a fragment it is somewhat under-specified rather than fully structured.

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 two-parameter calculator with full schema coverage, annotations, and an output schema, the description provides enough to understand the calculation and unit. Additional guidance on edge cases would improve it, but the core information is present.

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 both parameters documented as mass in kg and acceleration in m/s². The description’s formula maps those parameters into the computation, but adds little beyond the already complete 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 description states the exact physical formula F = m × a and the output unit (Newtons), so the resource and operation are clear. It does not differentiate this force calculator from nearby physics siblings such as weight, momentum, or acceleration.

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?

The formula implies the inputs, but there is no explicit guidance on when to use this tool versus alternatives like calculator_weight or calculator_physics_acceleration. No exclusions or decision context are provided.

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.