Skip to main content
Glama
devstacks-se

ID Generator MCP

by devstacks-se

ID 生成器 MCP

这是一个模型上下文协议 (MCP) 服务器,为 AI 助手提供 ID 生成功能。

安装

ID Generator MCP 可以与各种 AI 助手平台集成。以下是针对不同环境的说明:

克劳德·科德

要将 ID 生成器 MCP 添加到 Claude 代码,请运行以下命令:

claude mcp add id-generator npx @devstacks/id-generator-mcp

Cursor、Winsurf 或 Claude Desktop

要将 ID Generator MCP 添加到 Cursor、Winsurf 或 Claude Desktop,请将以下配置添加到您的 MCP 配置文件:

{
  "mcpServers": {
    "id-generator": {
      "command": "npx",
      "args": ["@devstacks/id-generator-mcp"]
    }
  }
}

Related MCP server: Magic Patterns MCP Server

用法

安装后,AI 助手可以使用 ID Generator MCP 生成各种类型的 ID。

支持的ID算法

算法

例子

描述

uuid

123e4567-e89b-12d3-a456-426614174000

UUID v4 - 通用唯一标识符,使用随机数生成一个 128 位值,冲突概率极低。该格式标准化,广泛应用于多种系统。

cuid2

clh3ppfqz0000jz0ggdlg7etk

针对水平扩展和性能进行了优化的抗冲突 ID。比 UUID 更短,同时保持唯一性。设计安全、URL 安全且顺序性强,可提高数据库性能。

nanoid

V1StGXR8_Z5jdHi6B-myT

小型、安全、URL 友好的唯一字符串 ID 生成器。创建紧凑、非序列化、URL 安全且高度抗冲突的标识符。默认长度为 21 个字符。

ulid

01ARZ3NDEKTSV4RRFFQ69G5FAV

通用唯一且按字典顺序排序的标识符。它将时间顺序的唯一性与随机唯一性相结合。26 个字符,采用 crockford base32 编码(无特殊字符),URL 安全,并可按字典顺序排序。

特征

  • 生成 UUID(v4)

  • 创建 CUID2 ID 以实现防碰撞识别

  • 生成 Nanoid 以获得紧凑、URL 友好的标识符

  • 为按时间排序的可排序标识符创建 ULID

  • 跨会话生成一致的 ID

  • 简单的 API 集成

  • 支持一次生成多个ID

执照

麻省理工学院

Available Tools

1 tool
generate-idD
ParametersJSON Schema
NameRequiredDescriptionDefault
algorithmNocuid2
quantityNo

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedgenerate-id

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate-id' has a clear, distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming is trivially consistent as there is only one tool. The tool name 'generate-id' follows a clear verb_noun pattern, and with no other tools to compare against, it maintains perfect consistency within the set.

Tool Count2/5

A single tool is too few for most server purposes, making the set feel thin and potentially incomplete. While 'generate-id' might be a simple utility, typical MCP servers benefit from a broader scope with 3-15 tools to handle related operations effectively.

Completeness1/5

The tool surface is severely incomplete. With only a 'generate-id' tool and no description, it lacks any context for the domain (e.g., UUIDs, custom IDs, batch generation) and misses obvious related operations like validation, listing, or deletion of IDs, leaving significant gaps for agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers