Skip to main content
Glama

Two-mass balance position

bpj_eng_center_of_mass
Read-onlyIdempotent

Determine the balance coordinate of two point masses along one axis.

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": {
      "massA": "<massA>",
      "xA": "<xA>",
      "massB": "<massB>",
      "xB": "<xB>"
    },
    "name": "bpj_eng_center_of_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault
xAYes
xBYes
massAYes
massBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds almost nothing on top: it does not state the underlying formula, the units of the result, or that the output is the mass-weighted mean position, all of which would be genuinely new information. For a pure calculation tool the annotation bar is low, but this text clears only the minimum.

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?

A single, front-loaded sentence with no filler or redundant restatement of the tool name. It is efficient, though its brevity is the same brevity that leaves the other dimensions thin.

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

Completeness2/5

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

With four required numeric parameters, no output schema, and zero schema description coverage, the description should explain what the returned value represents (a coordinate in meters on the same axis) and confirm the inputs are weighted by mass. Neither is present, so an agent cannot fully predict the result or validate its inputs from the definition alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description is expected to carry the burden of explaining the four required inputs, yet it only refers collectively to 'two point masses along one axis'. It never clarifies that xA/xB are coordinates in meters while massA/massB are weights in kilograms, or that both masses must be positive — the only hints come from the schema's parameter titles, not the description.

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 names a specific operation ('Determine the balance coordinate') and a specific object ('two point masses along one axis'), which is enough to distinguish it from the neighboring single-domain engineering calculators. It stops short of using the term 'center of mass' explicitly, so an agent must map 'balance coordinate' to the concept itself.

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, when not to, or what alternative exists (e.g. a general weighted-average or center-of-mass tool elsewhere in the catalog). The one-axis scope is the only implicit constraint on use, and the agent has to infer it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.