Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-creditCardNumber

Generates a random credit card number for testing and development, letting you specify an issuer name or card format to control the generated number.

Instructions

Generates a random credit card number.

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

Input Schema

NameRequiredDescriptionDefault
issuerNoThe name of the issuer (case-insensitive) or the format used to generate one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. 'Random' hints that output is synthetic, but it says nothing about Luhn validity, whether the issuer affects the prefix, whether values are safe for production, or whether any auth/rate limits apply.

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. Every word contributes to identifying the operation.

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?

For a simple one-optional-parameter generator with no output schema, the definition is minimally adequate but leaves gaps: it never mentions the issuer option or what the returned value looks like, and it gives no signal that the output is synthetic test data.

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%, and the sole 'issuer' parameter is documented in the schema as a case-insensitive name or format. The description adds no meaning beyond that, so the baseline of 3 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 names a specific verb ('Generates') and resource ('a random credit card number'), so an agent can tell this apart from finance-creditCardCVV or finance-creditCardIssuer by resource alone. It stops short of explicitly disambiguating against those close siblings, which is why it is not 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 or when-not-to-use guidance, no mention of alternatives like finance-creditCardIssuer, and no indication that this is test/fake data versus a real card source. The agent must infer all usage context from the name.

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