devtools-mcp

Generate Uuid

generate_uuid

生成 UUID（通用唯一识别码）。支持 v4 随机 UUID（默认）和 v5 命名空间 UUID（SHA-1 确定性生成，需提供 namespace 和 name）。count 可一次生成多个（1~1000）。namespace 支持预定义名 dns/url/oid/x500 或完整 UUID 字符串。

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

Input Schema

Name	Required	Description	Default
`name`	No	v5 必填，命名用的名称字符串，如域名、URL 等
`count`	No	生成数量，1~1000，默认 1
`version`	No	UUID 版本，"v4"（默认，随机）或 "v5"（命名空间确定性）	v4
`namespace`	No	v5 必填，命名空间，可传 "dns"/"url"/"oid"/"x500" 或完整 UUID 字符串

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / count / description
```
Added value: +"生成数量，1~1000，默认 1"
```
removedInput schema / properties / count / title
```
Removed value: -"Count"
```

addedInput schema / properties / name / description

Added value: +"v5 必填，命名用的名称字符串，如域名、URL 等"

removedInput schema / properties / name / title
```
Removed value: -"Name"
```

addedInput schema / properties / namespace / description

Added value: +"v5 必填，命名空间，可传 \"dns\"/\"url\"/\"oid\"/\"x500\" 或完整 UUID 字符串"

removedInput schema / properties / namespace / title
```
Removed value: -"Namespace"
```

addedInput schema / properties / version / description

Added value: +"UUID 版本，\"v4\"（默认，随机）或 \"v5\"（命名空间确定性）"

removedInput schema / properties / version / title
```
Removed value: -"Version"
```

removedInput schema / title

Removed value: -"generate_uuidArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does valuable work by explaining that v5 is deterministic (same namespace+name always yields the same UUID) and by bounding count at 1~1000, but it never states that generation has no side effects, that output is not persisted, or how the batch is returned. Adequate but not rich for an annotation-free tool.

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?

Four compact sentences, each front-loading the most useful fact: what it makes, the two versions, the count bound, and the namespace forms. No filler, though it is essentially a paraphrase of the schema rather than added information.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers both modes, defaults, and limits. The only gap is behavioral framing (side-effect free, non-persistent), which is minor for a pure generator with no annotations to contradict.

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 100%, so every parameter (name, count, version, namespace) is already documented, including the v5-required constraint and the dns/url/oid/x500 shortcuts. The description restates this information rather than adding new meaning, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb+resource (生成 UUID) and immediately distinguishes the two operating modes: v4 random (default) versus v5 namespace SHA-1 deterministic. An agent knows exactly what the tool produces and which mode it will get if it passes no arguments, which separates it cleanly from unrelated utility siblings like generate_qr or convert_timestamp.

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 is implied by the mode descriptions — an agent can infer it should pick v5 when it needs reproducible IDs — but there is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives. For a self-contained generator that may be sufficient, but the guidance is left to inference rather than stated.

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

All devtools-mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.