Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-productName

Generate a random descriptive product name for testing, seeding, or demo data. Use it to fill e-commerce catalogs with placeholder product titles without manual entry.

Instructions

Generates a random descriptive product name.

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": "commerce-productName"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose that output is random and descriptive rather than a real catalog value. It does not say whether the name is composed from adjective/material/product parts, whether results are deterministic or seedable, or what form the returned string takes.

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?

A single front-loaded sentence with no filler; the generator nature of the tool is conveyed in the fewest possible words. Nothing is repeated or padded.

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 zero-parameter random-string generator with no output schema, the description covers the essential fact that the result is a made-up product name. The only real gap is the absence of any indication of output shape (e.g., a plain string, number of words).

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?

The tool takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool 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?

States a specific verb and resource ("Generates a random descriptive product name"), so the agent knows exactly what comes back. It does not distinguish itself from nearby siblings such as commerce-product, commerce-productAdjective, or commerce-productMaterial, leaving the agent to infer that this one returns a full multi-word name.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The word "random" only implies a test-data/placeholder use case; the agent receives no routing signal versus the many other name-generator siblings.

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