Skip to main content
Glama

Generate a readable slug

bpj_make_readable_slug
Read-onlyIdempotent

Convert a title to a hyphen-separated slug with support for Unicode letters.

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": {
      "title": "<title>"
    },
    "name": "bpj_make_readable_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and repeatability are covered. The description adds one genuine behavioral detail beyond them — Unicode letters are supported — but says nothing about case folding, punctuation removal, diacritic transliteration, whitespace collapsing, or how the 300-character input limit interacts with output.

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?

A single front-loaded sentence with no filler and no repetition of the title or annotations. It is efficient, though it is short enough that a few more words of behavioral detail would have fit without harming readability.

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 one-parameter, read-only string transformation with no output schema, the definition covers input, output shape, and Unicode handling, which is close to sufficient. The main remaining gap is that the exact output conventions (lowercasing, diacritic handling) are not stated, and no output schema exists to compensate.

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?

Schema description coverage is 0%, but there is exactly one parameter named 'title' whose role the description restates as the conversion source, so nothing is ambiguous for the caller. The only unstated semantics — the maxLength of 300 and whether the input is trimmed — are visible in the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence gives a specific verb ('Convert') and a specific output resource ('hyphen-separated slug') from a stated input ('a title'), so an agent immediately knows what it produces. No sibling in the listed catalog performs slug generation, so there is nothing to differentiate against, but the definition also never says so explicitly.

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 only implied: the tool exists to turn a title into a slug, and that is a narrow enough job that no alternatives are strictly needed. There is no statement of when to prefer it, any preconditions, or any exclusions, leaving guidance at the 'obvious from the name' level.

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.