Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

commerce-price

Generate a random price within a specified minimum and maximum range, with optional decimal places and currency symbol for realistic commerce data.

Instructions

Generates a price between min and max (inclusive).

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

Input Schema

NameRequiredDescriptionDefault
decNoThe number of decimal places.
maxNoThe maximum price.
minNoThe minimum price.
symbolNoThe currency value to use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It never says the value is randomly generated, what happens when all four optional parameters are omitted (the schema marks zero required), or what defaults apply to dec and symbol — all material for a generator with no required inputs.

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?

It is a single front-loaded sentence with no filler and no repetition of structured fields. It is arguably over-terse, but nothing in it is wasted.

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

Completeness3/5

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

For a simple four-parameter generator with full schema documentation and no output schema, the description covers the core contract (bounds, inclusivity). It falls short on randomness, defaults for the entirely-optional parameter set, and the role of dec/symbol, which an agent still has to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines min, max, dec, and symbol. The description adds one genuinely useful semantic — that the bounds are inclusive — but says nothing about dec or symbol beyond what the schema states, so the baseline of 3 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?

The description uses a specific verb ('Generates') plus resource ('a price') and states the bounding behavior ('between min and max (inclusive)'), so an agent can tell it produces a value rather than validating or formatting one. It does not differentiate itself from the other commerce-* data generators beyond the resource name, which keeps it short of a 5.

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 statement of when to use this versus siblings like commerce-product or commerce-isbn, and no mention of the intended context (test/placeholder data generation). The only implied guidance is that a price falls in a min/max range.

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