Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

make_slug

Read-onlyIdempotent

utilpeek: Make a URL slug from text. For other case styles use text_case. Returns a URL slug: accents removed, Latin ligatures, Greek and Cyrillic transliterated, apostrophes dropped and other characters turned into one separator, cut at a separator when over max_length. CJK, Arabic, Hebrew, Indic, Thai and emoji are not romanised: they are dropped and counted in dropped_characters. Nothing left to slug is a 422 empty_slug (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/slug-generator-api.html

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": {
      "text": "<text>"
    },
    "name": "make_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text (at most 1,000 characters).
and_wordNoWrite & as this word, e.g. und; omit to drop &.
languageNoLetter rules: de ü->ue, da/nb/nn/no ø->oe å->aa, ca l·l->ll, sr/bs đ->dj; omit for ü->u.
lowercaseNoLower-case the slug.
separatorNo- (default) or _.-
max_lengthNoLongest slug; cut at a separator.

Output Schema

NameRequiredDescriptionDefault
slugNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
lengthNo
sourceNo
truncatedNo
transliteratedNo
dropped_charactersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / and_word / default
      Removed value: -null
    • removedInput schema / properties / and_word / title
      Removed value: -"And Word"
    • removedInput schema / properties / language / default
      Removed value: -null
    • removedInput schema / properties / language / title
      Removed value: -"Language"
    • changedInput schema / properties / lowercase / description
      Previous value: -"Lower-case the slug (default true)."New value: +"Lower-case the slug."
    • removedInput schema / properties / lowercase / title
      Removed value: -"Lowercase"
    • changedInput schema / properties / max_length / description
      Previous value: -"Longest slug (1-200, default 80); cut at a separator."New value: +"Longest slug; cut at a separator."
    • removedInput schema / properties / max_length / title
      Removed value: -"Max Length"
    • removedInput schema / properties / separator / title
      Removed value: -"Separator"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"make_slugArguments"
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed2 schema fields changed
    • addedInput schema / properties / and_word
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 20,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Write & as this word, e.g. und; omit to drop &.",
      +  "title": "And Word"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "de",
      +        "da",
      +        "nb",
      +        "nn",
      +        "no",
      +        "ca",
      +        "sr",
      +        "bs"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Letter rules: de ü->ue, da/nb/nn/no ø->oe å->aa, ca l·l->ll, sr/bs đ->dj; omit for ü->u.",
      +  "title": "Language"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "dropped_characters": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "length": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "slug": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "properties": {
      +        "library": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "transliterated": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "truncated": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantial context beyond them: the transliteration and separator rules, the fact that unromanisable scripts are dropped and counted in `dropped_characters`, the 422 empty_slug failure mode (and that it is not charged), latency, and price/free-tier limits. This is unusually complete behavioral disclosure for a mutating-looking string transform.

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?

Front-loaded with the core action and the sibling routing, then dense factual sentences with no filler. Slightly long because pricing, latency, and docs URL are appended, but each still informs a call decision.

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?

With an output schema present and full parameter coverage, the description supplies exactly the missing pieces: failure mode, dropped-character reporting, and cost. Nothing an agent needs to call this correctly is absent.

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%, so each of the six parameters is already documented in the schema, including the language enum rules and the max_length cut behavior. The description repeats the max_length cut-at-separator rule and does not add new meaning for `and_word`, `language`, or `separator` beyond the schema. Baseline 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 ("Make a URL slug from text") and immediately names the sibling it is not ("For other case styles use text_case"). An agent can distinguish it from text_case without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the alternative case-style use case to text_case, and adds a real usage gate by naming the scripts (CJK, Arabic, Hebrew, Indic, Thai, emoji) that will be silently dropped rather than romanised. An agent knows both when to pick this tool and when its input will degrade.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.