No capability to report current time or generate Discord timestamps #848

New issue

Closed

opened 2026-08-16 00:42:22 +00:00 by coilyco-ops-gaming · 1 comment

coilyco-ops-gaming commented

2026-08-16 00:42:22 +00:00

Member

Possible resolution: add a time/UTC conversion tool or integrate with an external clock service.

No tool or capability exists to report current time, UTC offset, or Discord timestamps. Requests like "what time is it in Paris" and "give me a Discord timestamp for 3pm today in Sydney" cannot be answered. Possible resolution: add a time/UTC conversion tool or integrate with an external clock service.

coilyco-ops-gaming added the

🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒

label

2026-08-16 00:42:22 +00:00

coilysiren commented

2026-08-16 01:16:25 +00:00

Owner

Unclear to me whats going on here. The relevant instruction is in the discord MCP as a resource

resource "discord-timestamps" uri="ward://discord/timestamps" mime="text/markdown" {
    description "How to render a time that every Discord reader sees in their own timezone"
    text "Discord renders a timestamp in EACH VIEWER'S OWN local timezone. Never compute a per-person time and never ask what timezone someone is in to display one. Emit the markup and let the client localise it."
    text ""
    text "Syntax: <t:EPOCH_SECONDS:STYLE>, or <t:EPOCH_SECONDS> which defaults to style f."
    text "EPOCH_SECONDS is Unix seconds, not milliseconds."
    text ""
    text "Styles, verified against Discord's developer reference on 2026-08-15:"
    text "  t  Short Time              16:20"
    text "  T  Medium Time             16:20:30"
    text "  d  Short Date              20/04/2021"
    text "  D  Long Date               April 20, 2021"
    text "  f  Long Date, Short Time   April 20, 2021 at 16:20   (the default)"
    text "  F  Full Date, Short Time   Tuesday, April 20, 2021 at 16:20"
    text "  s  Short Date, Short Time  20/04/2021, 16:20"
    text "  S  Short Date, Medium Time 20/04/2021, 16:20:30"
    text "  R  Relative Time           4 years ago"
    text ""
    text "Pick R for anything about how soon or how long ago, because it stays correct as it is re-read. Pick F when the exact day matters. Pick t when only the clock time matters and the day is already clear from context."
    text ""
    text "THE PART THIS DOES NOT SOLVE. Emitting the markup needs an epoch, and turning a phrase like Saturday 8pm into one needs the SPEAKER'S timezone. Discord does not expose member timezones over the API and nothing here can infer one. So ask the person, or repeat back the timestamp you assumed and let them correct it. Do not guess a timezone from a name, a language, or a channel."
}

So the issue is probably something like, the harness doesn't know how to tell you about resources

Unclear to me whats going on here. The relevant instruction is in the discord MCP as a resource ```kdl resource "discord-timestamps" uri="ward://discord/timestamps" mime="text/markdown" { description "How to render a time that every Discord reader sees in their own timezone" text "Discord renders a timestamp in EACH VIEWER'S OWN local timezone. Never compute a per-person time and never ask what timezone someone is in to display one. Emit the markup and let the client localise it." text "" text "Syntax: <t:EPOCH_SECONDS:STYLE>, or <t:EPOCH_SECONDS> which defaults to style f." text "EPOCH_SECONDS is Unix seconds, not milliseconds." text "" text "Styles, verified against Discord's developer reference on 2026-08-15:" text " t Short Time 16:20" text " T Medium Time 16:20:30" text " d Short Date 20/04/2021" text " D Long Date April 20, 2021" text " f Long Date, Short Time April 20, 2021 at 16:20 (the default)" text " F Full Date, Short Time Tuesday, April 20, 2021 at 16:20" text " s Short Date, Short Time 20/04/2021, 16:20" text " S Short Date, Medium Time 20/04/2021, 16:20:30" text " R Relative Time 4 years ago" text "" text "Pick R for anything about how soon or how long ago, because it stays correct as it is re-read. Pick F when the exact day matters. Pick t when only the clock time matters and the day is already clear from context." text "" text "THE PART THIS DOES NOT SOLVE. Emitting the markup needs an epoch, and turning a phrase like Saturday 8pm into one needs the SPEAKER'S timezone. Discord does not expose member timezones over the API and nothing here can infer one. So ask the person, or repeat back the timestamp you assumed and let them correct it. Do not guess a timezone from a name, a language, or a channel." } ``` So the issue is probably something like, the harness doesn't know how to tell you about resources

coilysiren referenced this issue

2026-08-16 01:17:00 +00:00

The harness doesn't know how to read MCP "resources" #851

coilysiren closed this issue

2026-08-16 01:17:08 +00:00