Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-currency

Generate a random currency object with code, name, symbol, and numeric code properties for testing, mock data, or locale-aware applications.

Instructions

Returns a random currency object, containing code, name, symbol, and numericCode properties.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key trait that the result is random rather than a fixed lookup, plus what fields come back. It says nothing about the value pool the random draw comes from, whether consecutive calls can repeat, or locality/format guarantees, which matter for a nondeterministic tool.

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?

One front-loaded sentence with no filler, and the essential information (random, currency object, listed fields) arrives immediately. It could be tightened only marginally, e.g. by grouping the field list more compactly.

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

Completeness4/5

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

For a zero-parameter generator with no output schema, the description is close to sufficient: it names the return shape and flags nondeterminism. The remaining gap is the absence of any statement about the range or source of the random values, which an agent might want when using the output in downstream logic.

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 an empty closed object, so there is nothing for the description to clarify beyond that. Baseline 4 applies for a parameterless tool.

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 concrete verb+resource ("Returns a random currency object") and enumerates the four fields it carries (code, name, symbol, numericCode), which implicitly separates it from the single-field siblings like finance-currencyCode or finance-currencySymbol. It stops short of naming any sibling, so an agent must infer the distinction rather than being told it.

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 or when-not-to-use guidance and no mention of alternatives such as the field-specific currency tools in the sibling set. The agent is left to decide entirely on its own when a whole random currency object is preferable to a single-property lookup.

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