Skip to main content
Glama

Kinematic viscosity unit converter

bpj_units_kinematic_viscosity
Read-onlyIdempotent

Convert kinematic viscosity in fluid datasheets. Enter one of m2/s, mm2/s, cSt, St, ft2/s to return the equivalent value in every listed unit.

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": {
      "value": "<value>",
      "unit": "<unit>"
    },
    "name": "bpj_units_kinematic_viscosity"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the key output behavior that is otherwise undocumented (no output schema): the result is the equivalent value in every listed unit. It omits precision/rounding, but adds real value beyond annotations.

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 sentences, no filler, with the action and the accepted units front-loaded and the return behavior last. Every clause earns its place.

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, stateless converter, the description covers input units and the output shape, which matters because there is no output schema. Minor gaps (precision, out-of-range handling) remain but are not blocking for correct invocation.

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 coverage is 0%, but the schema's field titles already enumerate the accepted units and the description repeats that list plus the mutual-exclusivity constraint (enter one of the five). It adds nothing about the numeric value's bounds (0 to 1e12) or invalid-unit handling, so it only partly compensates.

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 ("Convert kinematic viscosity") and scopes it to fluid datasheets, which also implicitly separates it from the sibling bpj_units_dynamic_viscosity. An agent can identify what it does and what it produces without opening the schema.

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?

Offers light context (fluid datasheets) but no explicit when-to-use/when-not guidance or named alternative among the many unit-converter siblings. Usage is implied rather than stated.

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.