Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-productDescription

Generates a fake product description for populating mock commerce catalogs, demos, and test data.

Instructions

Returns a product description.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it omits whether the returned string is randomly generated, deterministic, localized, or length-constrained. Only the bare fact of returning a description string is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single clean sentence with no padding, which is structurally fine. However, brevity here comes at the cost of under-specification rather than efficiency, since nothing beyond the name is communicated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of truth about the return value, and it says nothing about format, example content, randomness, or language. For a zero-parameter generator tool the definition is too thin to call reliably with confidence.

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, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The empty schema matches the description's implication of a no-argument call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns a product description" essentially restates the tool name (commerce-productDescription) without adding scope. It does not say whether this fetches the description of a specific product or synthesizes a random one, and among siblings like commerce-productName and commerce-productAdjective there is no stated differentiation.

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 when-to-use guidance, no prerequisite or context about which product (or none) is involved, and no mention of an alternative tool such as commerce-product itself. The agent must infer the purpose entirely.

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