Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-currencyNumericCode

Generates a random currency numeric code for testing, seeding sample financial data, or populating mock datasets with realistic currency identifiers.

Instructions

Returns a random currency numeric 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-currencyNumericCode"
  }
}

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, and it does disclose the key behavioral trait: the output is non-deterministic ('random'). It does not say what a numeric code looks like (digit count, ISO 4217 numeric range), whether the value is guaranteed to be a valid assigned code, or whether repeated calls can repeat values.

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 waste. For a zero-parameter generator there is nothing extraneous, and the operative detail ('random') is present.

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 is the only source of return-value information, and it stops at 'numeric code' without format, length, or validity guarantees. For a tool this simple that is nearly adequate, but the return contract remains underspecified.

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, so there is nothing for the description to disambiguate; baseline for a 0-param schema applies. The description correctly implies no inputs are required.

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 currency numeric code, qualified as random. An agent can tell this generates a value rather than looking one up. It does not, however, distinguish itself from the sibling finance-currencyCode, which an agent must infer is the alphabetic rather than numeric variant.

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 any alternative tool. The only hint of purpose is the word 'random', leaving the agent to guess that this is for test/sample data rather than real 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