Skip to main content
Glama

Decode a Discord snowflake

bpj_discord_snowflake_parts
Read-onlyIdempotent

Decode the Discord epoch timestamp, worker, process and increment fields of a snowflake.

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

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. What the description adds is the decomposition contract (the four fields produced), which substitutes partly for the absent output schema, but it says nothing about output format, ordering, or error behavior.

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; every term (epoch, worker, process, increment) carries information. It is arguably too terse rather than padded, so the only structural knock is the absence of a follow-up clarifying input expectations.

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 read-only decoding utility with annotations and no output schema, the description gives the essential shape of the result but leaves the input format and returned structure (e.g., timestamp as Unix seconds or ISO) unstated. Adequate to call the tool, not adequate to predict its output precisely.

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 single "value" parameter has no documented meaning other than its string type and 240-character cap. The phrase "of a snowflake" implies the value is a snowflake identifier, which is a modest clarification, but it does not state the expected format (decimal ID string) or that epoch-based timestamps are involved.

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 states a specific verb ("Decode") against a specific resource (a Discord snowflake) and enumerates the four components returned: epoch timestamp, worker, process, increment. That is concrete enough for an agent to recognize the operation, and the resource is distinctive enough against the sibling decoders, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no mention of what kind of input triggers it (a decimal snowflake ID string), and no note on invalid or non-snowflake input. The agent must infer all usage conditions from the name and title alone.

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.