Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-product

Generates a short fake product name for testing commerce data, helping populate sample catalogs without real product information.

Instructions

Returns a short 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-product"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It states only that a short product name is returned, without explaining whether the result is random, what 'short' means, whether it includes adjectives/materials, or what format to expect. For a generation tool, that leaves important behavioral questions unanswered.

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?

The definition is a single short sentence with no wasted wording and is front-loaded with the return behavior. It is concise, though the terseness contributes to the ambiguity rather than resolving it.

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?

For a simple zero-parameter generator, the description is still too thin: it does not clarify how the output differs from sibling tools, whether the value is random, or what a caller should expect. With no output schema, the description should do more to characterize the return value, and it does not.

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 no parameter semantics to document. The baseline for a parameterless tool is 4, and nothing in the description contradicts or complicates that.

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

Purpose3/5

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

The description names a verb and a resource ('Returns a short product name'), so the basic action is understandable. However, it does not distinguish this tool from the very similar sibling 'commerce-productName', which appears to serve nearly the same purpose. An agent cannot tell from this sentence which of the two to select.

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 use this tool versus alternatives such as commerce-productName, commerce-productDescription, or the other commerce-* generators. The description provides no context, exclusions, or selection criteria, leaving usage entirely implicit.

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