Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-department

Returns a fake shop department to help populate commerce datasets, store catalogs, and product examples with realistic department names.

Instructions

Returns a department inside a shop.

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

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?

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether data is randomly generated, not whether results are stable or repeatable across calls, not whether a shop context must already exist, and not what the response shape is. "Inside a shop" hints at domain context but not at behavior.

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 filler, and the resource is front-loaded in the first few words. Its brevity is efficient, though it shades into under-specification rather than tight, information-dense phrasing.

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, no output schema, and no parameters, the description is the only source of information about this tool, and it omits the return value entirely. For a data-generation tool, saying whether the output is a string or a structured object is essential and is missing.

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 meaning for the description to add; the empty schema and the description are consistent. Under the 0-parameter baseline this is a 4, with the only shortfall being that nothing is said about what is returned.

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?

"Returns a department inside a shop" gives a verb and a resource, and the phrase "inside a shop" adds a little scope beyond the name. However, for a faker-style generator it does not say what a "department" value actually is (a name string? an object with id and name?) nor does it distinguish this from siblings like commerce-product or commerce-price beyond the topic word.

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 mention of when a different commerce-* sibling should be chosen instead, and no stated preconditions. The agent is left to infer usage entirely from the tool 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