A
licenseNot graded
qualityB
maintenanceEnables AI agents to generate URL-friendly slugs from text with custom separators and transliteration, paid per call via x402 micropayments.
MIT
text-slugifier
Server Details
Converts text titles into URL-safe slugs and flags duplicates. x402 payment required (testnet USDC).
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 tooltext_slugifiertext_slugifierAInspect
Converts text titles into URL-safe slugs and flags duplicates. x402 payment required (testnet USDC).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| titles | Yes | Text titles to slugify | |
| payment | No | x402 payment payload (base64 JSON), signed EIP-712 exact/transferWithAuthorization. Omit on the first call — the tool will return payment requirements (accepts[]) as an error result. | |
| maxLength | No | Truncate slugs longer than this (default 80) |
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It explicitly discloses the x402 payment requirement and the fact that it flags duplicates, which are meaningful behavioral traits beyond the tool name. It doesn't detail error behavior, but the payment payload schema description already covers the first-call error flow.
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, dense sentence with no filler. The core action is front-loaded, followed by the essential payment caveat. Every word contributes useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool, the description plus schema cover the input parameters and payment workflow. However, there is no output schema and the description does not explain what the return value looks like or how duplicates are flagged, leaving some uncertainty for an agent.
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 description coverage is 100%, so the baseline of 3 applies. The description adds no parameter-level detail beyond what the schema already states, but the schema already documents titles, payment, and maxLength adequately.
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 uses a specific verb and resource: 'Converts text titles into URL-safe slugs and flags duplicates.' This clearly states the tool's function and outcome. Even without siblings, the purpose is unambiguous and distinct from the generic title.
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 intended use is clear: slugify text titles and flag duplicates. There are no sibling tools or exclusions to mention, so the absence of alternatives is not a gap. The x402 payment requirement also signals the operational context for using the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Normalizes and deduplicates a list of URLs. x402 payment required (testnet USDC, Base Sepolia).
11Pay-per-use AI and data tools via x402: image, video, music, voice, search, crypto. USDC.
x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks.
Pay-per-request webpage-to-Markdown extraction for AI agents. $0.005 USDC via x402 on Solana.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables URL shortening using a hash-based approach with pay-per-call via x402 micropayments on Base L2.MIT
- AlicenseAqualityCmaintenanceConverts PDF, Word, Excel, and PowerPoint documents to Markdown using a pay-per-conversion model with USDC on Base via the x402 protocol.2MIT
- FlicenseNot gradedqualityAmaintenanceWallet-funded remote MCP for live Solana priority fees, transaction simulation and diagnosis, token-risk checks, PDF-to-Markdown, and audio normalization. Paid tools use x402 on Solana and Base with no API key.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is singular and clearly described.
Naming Consistency5/5
With a single tool, naming consistency is trivially satisfied. The name text_slugifier is descriptive and matches the server's purpose, using snake_case consistently.
Tool Count3/5
A single tool is borderline for a purpose-built server; it feels thin even though the scope is narrow. The tool does one thing well, but the server offers no auxiliary operations.
Completeness4/5
The core slugification operation is covered, including duplicate flagging. Minor gaps such as configurable slug separators or batch processing would make it more complete, but the essential functionality is present.