Skip to main content
Glama

slugify

POST titles as JSON {"titles": [...]} or as raw text with one title per line, and get back URL-safe slugs. Strips accents, lowercases, removes apostrophes and collapses other punctuation to single hyphens. Up to 500 titles per call. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/slugify.

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

Input Schema

NameRequiredDescriptionDefault
titlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does a solid job: it discloses the transformation rules (strip accents, lowercase, drop apostrophes, collapse punctuation to single hyphens), the per-call limit of 500, and the pricing model (3 free calls/day per visitor, then $0.01 via x402). It does not describe the response shape (e.g., array vs newline output) or failure behavior when over the free limit, which keeps it from a 5.

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?

Two compact sentences, front-loaded with the input contract before the transformation rules, limits, and pricing. Every clause carries information, though the pricing/x402 sentence is dense enough that a reader must parse carefully.

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?

For a simple one-parameter, stateless transformation with no output schema, the description covers input format, normalization semantics, quantity limit, and cost. Missing only the output container format and error/rate-limit behavior when the free quota is exhausted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'titles' parameter has 0% schema description coverage, so the description must compensate, and it does: it names the accepted encoding ({"titles": [...]} or raw text, one title per line) and the 500-item ceiling. The only weakness is that the raw-text alternative is not representable in the declared object schema, which could confuse an agent about which shape to send.

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 transformation: takes POSTed titles (JSON array or raw newline text) and returns URL-safe slugs, with the exact normalization rules spelled out. This distinguishes it immediately from siblings like hash-encode or markdown-strip without needing to inspect their schemas.

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 input/output contract (give titles, get slugs), and the description adds practical context: the 500-title cap and the free-tier limit. However, it never says when to prefer this over alternatives, nor does it state any exclusion or precondition beyond the payment threshold.

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.

Resources