TeamPredict HR Calculators

Military (24-hour) time converter

military_time_convert

Read-onlyIdempotent

Convert between military (24-hour) time and standard 12-hour AM/PM time, in either direction. Give military_time (for example 1345, 13:45 or 0800) to get the standard time, or hour_12, minute and period to get the military time. Returns the converted time in every common written form, the plain-English name for special times (midnight, noon) and the hour of the military-time chart it sits in. Use military_shift_hours instead to find how many hours run between two military times.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "military_time_convert"
  }
}

Input Schema

Name	Required	Description
`minute`	No	The minute, 0 to 59, used with hour_12. Default 0.
`period`	No	AM or PM, used with hour_12.
`hour_12`	No	The hour on a 12-hour clock, 1 to 12. Use with period (and minute).
`military_time`	No	A military time such as 1345, 13:45, 945 or 2400 (end of day). Give this, or hour_12 with period.

Output Schema

Name	Required	Description
`inputs`	Yes	The inputs as used, with defaults filled in.
`results`	Yes	The computed numbers. Unavailable numbers are null.
`summary`	Yes	One or two plain sentences with the headline numbers.
`calculator_url`	Yes	The TeamPredict calculator page that shows the same calculation, where a person can change the inputs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds value by describing what comes back: every common written form, the plain-English name for midnight/noon, and the chart hour. That last part overlaps somewhat with the existing output schema, keeping it just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences, front-loaded with the core conversion and followed by input routing and an alternative. Minor waste in the return-value sentence, which partly restates what the output schema will already show.

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?

Given a simple 4-parameter, zero-required tool with full schema coverage, annotations and an output schema, the description covers purpose, both input paths, accepted formats and sibling routing. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: it shows accepted input formats for military_time ('1345, 13:45 or 0800') and reveals that colon-separated and bare forms are both valid, which the schema's maxLength 10 alone does not convey. It also clarifies the either/or relationship between the two input paths.

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?

States a specific verb (convert) and resource (military/12-hour time), explicitly bidirectional, and names the sibling it is not (military_shift_hours) with the reason. An agent can distinguish it from the other time tools without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit input paths — 'Give military_time ... to get the standard time, or hour_12, minute and period to get the military time' — and explicitly routes the interval use case to military_shift_hours. Both when-to-use and the alternative are spelled out.

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

All TeamPredict HR Calculators 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?