Skip to main content
Glama

Discord timestamp codes

discord_timestamp
Read-onlyIdempotent

Make Discord timestamp codes like <t:1767225600:F> that show a date and time in every reader's own time zone, for event announcements and stream schedules. Pass an ISO 8601 date-time with its UTC offset (e.g. "2026-12-31T20:00:00-05:00") or a Unix timestamp in seconds. Returns all seven 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": {
      "time": "<time>"
    },
    "name": "discord_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesISO 8601 date-time including the UTC offset or Z, or Unix seconds. Ask the user for their time zone if it isn't known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, non-destructive local read. The description adds behavior the annotations cannot convey: the output is rendered in every reader's own time zone, and all seven formats are returned. It doesn't enumerate the seven format specifiers, leaving some output detail implicit.

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?

Three short sentences, front-loaded with the action, then the use case, then input formats, then output. No filler or hedging, and the example output appears early where it aids recognition.

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 one-parameter, no-output-schema tool, the definition covers purpose, input formats, and the shape of the return value (all seven formats). Listing the seven specifiers would make it fully self-contained, but an agent can call it correctly as written.

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 coverage is 100% and there is a single parameter, so the schema already documents accepted formats and the time-zone caveat. The description's example (`"2026-12-31T20:00:00-05:00"`) largely restates the schema; it adds little beyond confirming the offset requirement. Baseline 3 is appropriate.

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 names a specific verb and resource ("Make Discord timestamp codes") and shows a concrete output example `<t:1767225600:F>`, so the agent knows exactly what will be produced. This is unmistakably distinct from every sibling tool (coin converters, earnings estimators, text stylers).

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 a clear purpose context ("for event announcements and stream schedules") and specifies acceptable inputs (ISO 8601 with UTC offset, or Unix seconds). It does not name an alternative or state when-not to use it, but no sibling overlaps, so that gap is minor.

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