Skip to main content
Glama

Dynamic viscosity unit converter

bpj_units_dynamic_viscosity
Read-onlyIdempotent

Convert dynamic viscosity in fluid datasheets. Enter one of Pa.s, mPa.s, cP, P, lb/(ft.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_dynamic_viscosity"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral value by stating the return shape - the equivalent value in every listed unit - which matters because no output schema exists. It does not mention precision, rounding, or how the multi-unit result is keyed.

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?

Two compact sentences with the purpose front-loaded and the input method second. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a simple two-parameter converter with no output schema, the definition covers the essentials: accepted units and the fact that all units are returned. It is still thin on output structure (map vs. list), rounding behavior, and unit-string matching rules, which an agent would need to use results reliably.

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 0%, so the description must carry the parameter meaning, and it does enumerate the accepted unit strings. However, that enumeration also appears in the schema title, and the description says nothing about case sensitivity, the numeric bounds (0 to 1e12), or output precision for `value`.

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 a specific verb and resource ("Convert dynamic viscosity") plus the domain of use (fluid datasheets), and the explicit unit list separates it from the kinematic-viscosity sibling. It does not name a sibling or exclusion directly, so it stops short of a 5.

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?

"Enter one of Pa.s, mPa.s, cP, P, lb/(ft.s)" tells the agent how to invoke it and the datasheet context implies when it is appropriate. There is no explicit when-not guidance or routing to alternatives such as the kinematic viscosity converter.

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.