Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-slug

Generate hyphen-separated slug text from a specified word count or range for URLs, filenames, and placeholder data.

Instructions

Generates a slugified text consisting of the given number of hyphen separated words.

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

Input Schema

NameRequiredDescriptionDefault
wordCountNoThe number of words to generate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the output shape (hyphen-separated slugified words), but says nothing about randomness/determinism, casing, allowed character set, or what happens if wordCount is omitted even though the parameter is optional.

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 efficient sentence with the key noun phrase front-loaded and no filler. Minor awkwardness in 'slugified text consisting of ... hyphen separated words' but nothing wasted.

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 single-parameter utility the description covers what is produced, but omits the optional-parameter default and any note on output variability. Adequate, though a caller still cannot predict exactly what it gets when wordCount 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 description coverage is 100%, so the wordCount parameter and its min/max range object are already documented in the schema. The description adds only a restatement of 'the given number of words' and does not explain the range-object form or default behavior.

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?

States a specific verb ('Generates') and resource ('slugified text ... hyphen separated words'), which distinguishes it from sibling word/text generators by output format. It stops short of explicitly naming a sibling alternative.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no pointer to the many sibling lorem generators (lorem-word, lorem-words, lorem-sentence, etc.). The agent must infer that this tool is the slug variant from the description alone.

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

Deploy Server

Other Tools