Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-amount

Generate a random monetary amount between inclusive minimum and maximum bounds, with configurable decimal places, currency symbol, and number formatting for testing and mock financial data.

Instructions

Generates a random amount between the given bounds (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": "finance-amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
decNoThe number of decimal places for the amount.
maxNoThe upper bound for the amount.
minNoThe lower bound for the amount.
symbolNoThe symbol used to prefix the amount.
autoFormatNoIf true this method will use Number.toLocaleString(). Otherwise it will use Number.toFixed().

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two genuinely useful traits — the output is random, and the bounds are inclusive — but it is silent on default values for the five optional parameters, what happens if min exceeds max, and what the returned value looks like (number vs. symbol-prefixed string).

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the scope ('between the given bounds') is stated immediately after the verb. Nothing can be trimmed without losing information.

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 five optional parameters and no required ones, the tool can be called with no arguments, yet the description never says what the defaults are or what the return value looks like — and there is no output schema to fall back on. For a generator whose entire output is the unstated part, this leaves a meaningful gap.

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 description coverage is 100%, so each parameter is already documented and the 3 baseline applies. The description adds one real clarification, that both bounds are inclusive, but says nothing about defaults, ordering constraints, or how dec/autoFormat/symbol interact with the generated value.

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 gives a specific verb and resource ('Generates a random amount') plus the range semantics ('between the given bounds'), so an agent knows exactly what the tool produces. It does not distinguish itself from the many other finance-* generators by naming any alternative, 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 when-to-use statement, no prerequisites, and no mention of when a different sibling (e.g., finance-currencySymbol or finance-currencyCode) would be more appropriate. The purpose is self-evident enough that an agent could infer usage, but the description contributes no routing guidance.

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