Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

snowflake_info

Read-only

Converts Discord IDs to creation timestamps or timestamps to IDs for before/after cursors.

Instructions

Convert a Discord ID to its creation time, or a time to an ID (for before/after cursors).

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": "snowflake_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
timeNoISO8601 time

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the description does not need to restate safety. It adds the semantic frame (creation-time extraction and cursor construction) but omits notable behavior detail such as Discord's snowflake epoch differing from Unix epoch and the exact output format for each direction.

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?

A single sentence that front-loads the operation and reserves the parenthetical for use context. No filler or repeated information.

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 zero-required-parameter utility tool with no output schema, the definition should clarify that exactly one of id or time is expected and what the return type looks like in each direction. Those gaps remain, though the core conversion semantics are covered.

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 50%: the time property is documented as 'ISO8601 time' while id is a bare string. The description compensates partially by identifying id as a Discord ID and tying time to before/after cursors, but it never states that the two parameters are alternatives or how their conversion directions are selected.

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?

The description gives a concrete bidirectional operation: 'Convert a Discord ID to its creation time, or a time to an ID,' which tells an agent exactly what resource pair is involved. It is not differentiated from any named sibling, though in practice no sibling in the list does snowflake conversion, so confusion risk is low.

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?

Usage context is implied by '(for before/after cursors),' which signals the main reason an agent would call it. It does not state what happens when both id and time are supplied, nor which argument takes precedence (

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

Deploy Server

Other Tools