Hopi

Slug generator

hopi_slug_generator

Read-onlyIdempotent

Turn any title or text into a clean URL slug: lowercase, accents stripped, and every run of spaces, punctuation and symbols collapsed to a single hyphen, with hyphens trimmed from the ends. Source: https://hopi.co.uk/slug-generator/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	The title or text to slugify

Output Schema

TableJSON Schema

Name	Required	Description
`slug`	No
`length`	No
`summary`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds detailed behavioral rules beyond the annotations: lowercase, accent stripping, collapsing to a single hyphen, trimming edges. This is exactly the kind of context an agent needs to predict output. No contradiction with readOnlyHint/idempotentHint.

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 a single, well-structured sentence that front-loads the core purpose and then specifies rules and a source link. No wasted words.

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?

The tool is simple with one input, an output schema, and annotations. The description covers the transformation rules and input purpose, making it complete for correct invocation. No missing details.

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% and the schema parameter description already states 'The title or text to slugify'. The tool description repeats the same idea and adds algorithm context but doesn't add new parameter-specific semantics. Baseline 3 is appropriate.

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 states a specific transformation (turn title/text into a URL slug) and enumerates exact rules: lowercase, accent stripping, collapsing runs to a single hyphen, trimming edge hyphens. This clearly distinguishes it from sibling tools like url_encoder or case_converter.

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

Usage Guidelines4/5

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

The description clearly implies usage for creating URL slugs from arbitrary text. It doesn't explicitly name alternatives or exclusion conditions, but the purpose is unambiguous and no competing tool in the sibling list serves the same function, so the context is clear.

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

All Hopi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?