Skip to main content
Glama

Duration unit converter

bpj_units_duration
Read-onlyIdempotent

Convert fixed-length time intervals. Enter one of s, ms, us, min, h, d, wk 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_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 covered. The description adds useful return-shape information — the result covers every listed unit, not just one — which is meaningful since no output schema exists. It says nothing about rounding, precision, or how the value is normalized, which are the remaining behavioral gaps.

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 action and the accepted input set front-loaded. Every clause — including the fixed-length qualifier — carries information the agent needs to call the tool correctly.

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, read-only converter the definition covers purpose, valid unit tokens, and the shape of the result. Notes on precision or output formatting would close the remaining gap, but nothing essential for correct invocation is missing.

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% and there is no enum on the unit parameter, so the description's enumeration of allowed unit strings carries real weight and fully compensates for that gap. However, the second parameter (value) gets no semantic treatment beyond what the schema's numeric bounds provide, leaving a 0%-coverage schema only half remedied in prose.

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?

"Convert fixed-length time intervals" gives a specific verb plus a scoped resource, and the enumerated unit set (s, ms, us, min, h, d, wk) makes clear this is the time-domain member of the units_* family rather than length, mass, or temperature. It stops short of naming or contrasting with any sibling converter, so it is clear but not sibling-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Enter one of s, ms, us, min, h, d, wk" tells the agent exactly what input qualifies, and the qualifier "fixed-length" implicitly excludes calendar-dependent spans like months or years. There is no explicit when-to-use/when-not statement or pointer to an alternative for non-fixed intervals, so the guidance is clear but not complete.

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.