devutils-mcp-server

generate_nanoid

Generate NanoIDs: compact, URL-friendly unique identifiers. Customize length (1-128) and count (1-100) for use in tokens, keys, or slugs.

Instructions

Generate a NanoID — a compact, URL-friendly unique ID.

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

Input Schema

Name	Required	Description	Default
`length`	No	Length of the NanoID (1-128, default: 21)
`count`	No	Number of IDs to generate (1-100, default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 24, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are available, and the description does not disclose any behavioral traits such as randomness source, security properties, or potential side effects. It adds minimal value beyond the tool's name.

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?

The description is one concise sentence (16 words) that is front-loaded with the action and resource. Every word serves a purpose, with no fluff.

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?

Given the simplicity of the tool (no output schema, no nested objects), the description adequately explains what a NanoID is. It covers the core functionality, though it could mention the default character set for completeness.

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?

Input schema has 100% description coverage for both parameters (length and count), so the schema already provides clear semantics. The description does not add further meaning, thus a baseline score of 3.

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?

The description 'Generate a NanoID — a compact, URL-friendly unique ID' uses a specific verb and resource, clearly distinguishing it from sibling tools like generate_uuid. It accurately describes what the tool does.

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?

The description implies usage for URL-friendly IDs but does not explicitly state when to use this over alternatives like generate_uuid or generate_password. No exclusions or when-not-to-use guidance is provided.

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