Skip to main content
Glama

Decode a ULID timestamp

bpj_ulid_components
Read-onlyIdempotent

Extract the millisecond timestamp and encoded randomness from a Crockford Base32 ULID.

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_ulid_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the safety profile needs no repetition. The description adds useful behavioral substance by naming the two decoded components, but says nothing about behavior on malformed input or the shape/order of the returned fields, which matters since there is no output schema.

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 front-loaded sentence naming the input format and the two outputs, with no filler or redundant restatement of the title.

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 one-parameter decoder this is close to adequate, but with no output schema the agent still cannot know the return structure (object with two fields? formatted string?) or how invalid ULIDs are reported. A clause on the return shape or failure mode would close the gap.

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 must carry the load, and it does establish that the 'value' parameter is a Crockford Base32 ULID. However it does not explain the maxLength of 240 or what characters are valid, leaving gaps the schema does not fill.

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?

States a specific verb ('Extract') plus the exact outputs (millisecond timestamp and encoded randomness) and the input format (Crockford Base32 ULID). An agent can tell it decodes ULIDs rather than generating them, though it never explicitly contrasts with the sibling bpj_objectid_components or other decoders.

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 explicit when-to-use statement, no mention of alternatives such as bpj_objectid_components or bpj_convert_timestamp, and no note on error conditions. Usage is only implied by the tool name and the word 'ULID' in the description.

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.