Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-productMaterial

Returns a product material value for seeding e-commerce test data. Use it to populate merchandise records with material details such as cotton or leather.

Instructions

Returns a material of a product.

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

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, the description carries the full disclosure burden, yet it doesn't say whether this returns a random sample, a fixed lookup, or a localized string, nor the value's shape or length. For a zero-parameter value generator the key behavioral fact, that it produces a standalone data value, is left implicit.

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 no redundancy. It is front-loaded and earns its place, though it is under-specified rather than wasteful.

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 trivial zero-param generator, the description should at minimum convey what kind of value comes back (a short label, a category string) and that no product context is needed. Neither is present, and there is no output schema to fill the gap.

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 empty, so there is nothing for the description to disambiguate. The 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.

Purpose3/5

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

States a verb and a resource: "Returns a material of a product." However, "material" is ambiguous (fabric? substance? raw material?) and the sentence gives no way to tell this apart from siblings like commerce-product, commerce-productAdjective, or commerce-productName, all of which look like single-value data generators.

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?

The description gives no guidance on when to use this versus the many sibling value generators, no preconditions, and no exclusions. The agent must infer that this produces a product-material value purely from the name.

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