Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-sentences

Generate a specified number of Lorem Ipsum sentences, with optional count ranges and separators, to create placeholder text for layouts, mockups, and test data.

Instructions

Generates the given number of sentences.

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-sentences"
  }
}

Input Schema

NameRequiredDescriptionDefault
separatorNoThe separator to add between sentences.
sentenceCountNoThe number of sentences to generate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. It doesn't say the output is random/non-deterministic lorem text, what form the result takes (string vs array), or what happens when sentenceCount is a min/max range.

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 short sentence with the key information front-loaded and no filler. It is efficient, though its brevity borders on under-specification rather than tightness.

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 two-parameter generator with fully described params and no output schema, the description is minimally adequate. It still leaves the agent guessing about output shape and randomness, which matters for a generation tool.

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 both separator and sentenceCount (including the min/max object form) are already documented in the schema. The description's phrase 'the given number of sentences' only echoes sentenceCount and adds nothing about the separator or range semantics; baseline 3 applies.

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 description states a specific verb ('Generates') and resource ('sentences') with a quantity qualifier, so the agent knows exactly what it produces. It does not distinguish itself from near siblings like lorem-sentence (singular) or lorem-paragraphs, so it falls short of a 5.

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?

There is no guidance on when to pick this over lorem-sentence for a single sentence or lorem-text/lorem-paragraphs for larger blocks. The agent must infer the distinction from tool names 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