Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-currencyCode

Generates a random currency code to populate test data and finance prototypes with sample ISO currency values.

Instructions

Returns a random currency code.

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

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, the description carries the full burden; it does disclose the key trait that output is random, which is genuinely useful. However it says nothing about the distribution, whether results repeat, whether the random source is seeded or reproducible, or the format/length of the returned code. Adequate but with clear gaps for a zero-param generator.

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 filler or redundancy. Every word earns its place and the reader knows the operation immediately.

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?

No output schema exists, so the description should characterize the return value, yet it never specifies the code format (e.g. ISO 4217 three-letter uppercase) or whether values can repeat. For a trivial zero-param tool this is close to sufficient, but the missing output-format detail leaves a real gap.

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 no parameters and the schema is an empty object, so there is nothing to disambiguate; baseline 4 applies. The description correctly adds no parameter claims that would conflict with the empty schema.

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?

States a specific verb and resource ('Returns a random currency code'), and the word 'code' plausibly distinguishes it from sibling generators like finance-currencyNumericCode and finance-currencyName. It does not explicitly name those siblings or confirm the output is an alphabetic ISO-style code, so differentiation is inferred rather than stated.

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 alternatives such as the numeric-code or currency-name generators, and no context about when a random code is useful (e.g. seeding test data). The agent must infer purpose entirely from the one sentence.

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