Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-currencyName

Generate a random currency name for testing, mock data, or populating finance-related fields without external data.

Instructions

Returns a random currency name.

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

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?

No annotations exist, so the description carries the full burden. It usefully discloses the key behavioral trait that the output is non-deterministic, which is essential for an agent to know, but it omits the returned format (e.g. "US Dollar" vs "USD") and any distribution guarantees, leaving gaps for a generator tool.

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 no wasted words. The core fact, randomness and the resource, arrives first.

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?

There is no output schema, so the description is the only place to learn what a caller gets back, and it does not specify the string format. For a simple zero-input generator this is a modest but real gap when the agent must choose among similarly named currency tools.

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 description correctly implies that no input is needed. With an empty schema there is nothing further to document, so the baseline of 4 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 gives a specific verb and resource ("Returns a ... currency name") and the qualifier "random" sets it apart from deterministic lookups like finance-currencyCode or finance-currencySymbol in the sibling set. It stops short of explicitly naming how it differs from finance-currency, so it is clear but not fully differentiated.

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 tool versus the other finance-* siblings (currency, currencyCode, currencyNumericCode, currencySymbol), nor any exclusions or prerequisites. The agent has to infer that this is for generating sample data.

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