devutils-mcp-server

slugify

Convert any string into a URL-friendly slug by removing special characters, replacing spaces with hyphens, and converting to lowercase.

Instructions

Convert a string to a URL-friendly slug. Removes special characters, replaces spaces with hyphens, and lowercases everything.

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": {
      "input": "<input>"
    },
    "name": "slugify"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	The string to slugify

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It explicitly states three behavioral traits (removing special characters, replacing spaces, lowercasing). However, it does not specify handling of consecutive hyphens or leading/trailing hyphens, which are typical edge cases for a slugify.

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?

Description is two sentences, front-loaded with the main action, and every word is essential. No fluff.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description adequately covers input and processing steps. An agent can correctly invoke this tool based on the description alone.

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 coverage is 100% with a single parameter 'input' described as 'The string to slugify'. The description does not add additional semantic meaning beyond that; it is a straightforward parameter.

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?

Description clearly states verb 'Convert', resource 'string to URL-friendly slug', and specifies three transformations: removes special characters, replaces spaces with hyphens, lowercases. No sibling tools overlap; purpose is distinct.

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?

Description does not provide explicit usage guidelines or compare with alternatives. The tool's purpose is self-evident, but for a more complete definition, it could mention when to use slugify over other string manipulation tools.

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