Skip to main content
Glama

Electrical charge unit converter

bpj_units_electrical_charge
Read-onlyIdempotent

Convert ampere-hours, battery charge, and coulombs. Enter one of C, mC, uC, Ah, mAh 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_electrical_charge"
  }
}

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 readOnly, idempotent, closed-world, non-destructive behaviour, so the bar is lower; the description adds the key output trait that the result covers every listed unit, not just one target unit. It stops short of mentioning rounding/precision or significant digits.

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, zero filler, with the resource scope front-loaded and the input/output contract in the second sentence. 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.

Completeness5/5

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

For a two-parameter, closed-world converter with no output schema, the description covers input format, accepted units, and the multi-unit result shape. No material gap remains for correct invocation.

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 description coverage is 0%, so the description has to carry the parameter meanings, and it does: it enumerates the accepted unit strings (C, mC, uC, Ah, mAh) and frames value as the quantity to convert. The ±1e12 value bounds and sign handling remain undocumented in prose, but those are already encoded in the 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?

Names a specific verb (convert) and the concrete resource domain (ampere-hours, coulombs, battery charge), plus the exact unit set handled. This cleanly separates it from the neighbouring bpj_units_* converters, though no sibling is named explicitly.

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?

The description tells the agent what to supply ('Enter one of C, mC, uC, Ah, mAh'), which implies the calling context, but gives no explicit when-to-use framing and no exclusions or alternatives (e.g. when to pick this over bpj_units_energy or a generic unit tool).

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.