Skip to main content
Glama

convert_duration

Convert a duration between units and get it in plain language. Use it to express a timeout in the unit the caller asked for, or to check whether a limit is seconds, minutes or milliseconds. ($0.003 per call)

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>"
    },
    "name": "convert_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNothe unit to convert intoseconds
fromNothe unit of valueseconds
valueYesthe magnitude

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?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the per-call cost and that output is plain language, but it does not state whether the operation is purely computational, how rounding or precision is handled, or what errors may occur.

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?

The description is two short sentences plus a cost note, with the core purpose front-loaded. Every sentence contributes useful information without redundancy.

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 low-complexity conversion tool with a fully described schema, the description covers purpose, usage, output style, and cost. It is nearly complete, though without an output schema it could specify the exact return format or precision more explicitly.

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 100%, and the schema already defines value, from, and to with enums and defaults. The description implies unit conversion but adds no parameter-specific details beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb and resource: "Convert a duration between units," and adds that the result is in plain language. It is clear what the tool does, though it does not explicitly differentiate itself from nearby tools such as add_duration.

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?

It gives concrete usage scenarios: expressing a timeout in the caller's requested unit, or checking whether a limit is in seconds, minutes, or milliseconds. It does not explicitly state when not to use it or name alternatives, which keeps it below a 5.

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.

Resources