Skip to main content
Glama

Convert timestamps

bpj_convert_timestamp
Read-onlyIdempotent

Convert explicitly specified Unix seconds, milliseconds, or an ISO timestamp with an offset into three time formats.

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": {
      "format": "<format>",
      "value": "<value>"
    },
    "name": "bpj_convert_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
formatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the accepted input families and states that three output formats are produced, but never names those formats or explains error behavior for malformed input — modest extra context above the annotations.

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?

A single front-loaded sentence with no filler or repetition. The slightly opaque phrase 'explicitly specified' costs a bit of clarity but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a two-parameter, no-output-schema utility this is close to adequate, but the agent cannot predict the returned structure or the three target formats, nor the timestamp bounds or offset syntax. Given how simple the tool is, one more clause would have made it complete.

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%, so the description carries the burden, and it does partially compensate: it clarifies that the format parameter takes seconds, milliseconds, or an ISO string and that ISO input must carry an offset. It still omits accepted spellings, numeric ranges, and what 'three formats' means for the output, leaving the value/format pairing only loosely specified.

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 resource (timestamps) and enumerates the accepted input kinds (Unix seconds, milliseconds, ISO with offset), which is more precise than the title. It does not, however, distinguish itself from the sibling bpj_convert_fixed_offset_time, and 'three time formats' is left unspecified.

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 word 'explicitly specified' implies the value must be a concrete literal rather than a relative expression like 'now', which is useful implied guidance. There is no explicit when-to-use/when-not-to-use statement and no routing to the fixed-offset sibling, so the agent must infer the boundary.

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.