Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Slugify, make a URL slug: turn a title into a clean URL slug

slug
Read-only

Turn any text into a URL-friendly slug: accents removed (é→e, ß→ss), lower case, non-alphanumerics replaced by a separator (- by default). Use for file names, URLs and IDs. Example: text=Crème Brûlée & Straße!. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text
separatorNo- (default) or _

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only declare read-only/no-destroy/no-open-world; the description adds the things an agent cannot infer structurally: the cost ($0.01/call via x402 USDC or a card key at /credits), the 25-free-call allowance, that failed calls are free, and that repeats are billed again. That last clause usefully explains why idempotentHint is false for a pure function, which would otherwise look like an annotation error.

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 verb and transformation, then uses, then the example, then billing and safety. The billing sentences are dense and semicolon-heavy, but each clause (price, payment rails, free tier, failure policy, per-call charge) carries information an agent needs before spending money, so nothing is filler.

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 two-parameter pure transformation with full schema coverage and no output schema, the only real gaps are the returned value's format (a plain slug string) and behavior on an unrecognized separator value. Everything an agent needs to call it correctly and to understand cost and side-effect freedom is present.

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 coverage is 100%, so the baseline is 3, but the description earns above that by explaining the semantic effect of both parameters: the accent-folding and case rules that apply to text, and that separator defaults to "-" and is substituted for non-alphanumerics. The example demonstrates the interaction of text and default separator rather than restating field names.

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?

"Turn any text into a URL-friendly slug" gives a specific verb and resource, then pins down the exact transformation rules (accents removed é→e, ß→ss, lower case, non-alphanumerics replaced by separator) plus a worked example. An agent can predict the output shape without calling the tool or opening the schema.

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?

"Use for file names, URLs and IDs" names concrete contexts, which is more than most sibling tools get. It stops short of exclusions or routing advice (e.g., when to prefer url_encode or case from the sibling set, or that this is not reversible decoding), so it is clear but not fully disambiguating.

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.