Skip to main content
Glama

Magnetic flux unit converter

bpj_units_magnetic_flux
Read-onlyIdempotent

Convert coil and instrument magnetic flux. Enter one of Wb, mWb, uWb, Mx 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_magnetic_flux"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuine behavioral value with 'return the equivalent value in every listed unit', which discloses the response shape absent an output schema. It stops short of stating rounding/precision or what happens with an unrecognized unit string.

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 short sentences with zero filler; the purpose comes first and the calling convention immediately follows. Nothing could be removed without losing information.

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 read-only converter with no output schema, the definition covers purpose, accepted units, and the fact that all units are returned. A brief note on precision or invalid-unit handling would make it fully self-sufficient.

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

Parameters4/5

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

Schema coverage is 0% and the unit parameter has no enum, so the description carries the burden — and it does by enumerating the four accepted unit symbols (Wb, mWb, uWb, Mx), which is information the schema does not contain. The value parameter is only described as an 'Input value', adding little beyond the schema's numeric bounds.

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?

States a specific verb (Convert) and resource (coil and instrument magnetic flux), and names the exact unit set Wb, mWb, uWb, Mx, so the agent knows precisely which quantity is handled. It does not explicitly contrast itself with the sibling bpj_units_flux_density (a different physical quantity), leaving that separation to be inferred from the domain terms.

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: 'Enter one of Wb, mWb, uWb, Mx' tells the agent how to call it but never states when to pick this converter over a sibling like flux density or when not to use it. No prerequisites, no exclusions, no named alternatives.

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.