Hopi

Military time converter

hopi_military_time_converter

Read-onlyIdempotent

Convert between 24-hour (military) time and 12-hour clock time. Direction '24h-to-12h' takes a 24-hour time like '1430' or '14:30'. Direction '12h-to-24h' takes a 12-hour time like '2:30' with a meridiem of am or pm (the meridiem can also be written in the time string). Source: https://hopi.co.uk/military-time-converter/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`time`	Yes	The time to convert, e.g. '1430', '14:30', '2:30 pm'
`meridiem`	No	am or pm for 12h-to-24h when not in the time string (default pm)	pm
`direction`	Yes	Which way to convert

Output Schema

TableJSON Schema

Name	Required	Description
`time12`	Yes
`time24`	Yes
`summary`	Yes
`meridiem`	Yes
`direction`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "direction",
+  "meridiem",
+  "source_url",
+  "summary",
+  "time12",
+  "time24"
+]

First observedSep 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by explaining what each direction accepts and giving concrete examples like '1430', '14:30', and '2:30' with a meridiem. It does not discuss edge cases such as invalid input or 2400 handling, but that is a minor gap.

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 compact and front-loaded: purpose first, then direction-specific behavior and examples. Every sentence contributes useful information, and the source attribution is a minor, acceptable addition.

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 converter with an output schema, the description plus parameter schema cover what an agent needs to call the tool correctly. The only slight omission is explicitly stating the default meridiem behavior when none is supplied, though the schema's default of 'pm' covers this.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds value by showing example formats for the 'time' parameter and clarifying that the meridiem can be provided either separately or inline in the time string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Convert') and the exact resource (24-hour military time vs 12-hour clock time), making the tool's purpose immediately clear. It also names the two direction values, which distinguishes it from other converter-style siblings.

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?

The description clearly implies when to use this tool: whenever a time needs converting between 24-hour and 12-hour formats. It does not explicitly mention alternative sibling tools or list exclusion cases, so it falls just short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hopi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?