Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-maskedNumber

Generate a random masked number with configurable length, mask character, parentheses, and ellipsis to create test financial data.

Instructions

Generates a random masked 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-maskedNumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe length of the unmasked number.
parensNoWhether to use surrounding parenthesis.
ellipsisNoWhether to prefix the number with an ellipsis.
maskCharNoThe character to use as a mask.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. 'Random' implies non-determinism, but it does not state that the tool is side-effect free, whether the result is a string, what the masked output looks like, or that the generated value is fake data. These are meaningful gaps for a tool with zero annotation coverage.

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?

It is a single front-loaded sentence with no redundant wording. Its brevity reflects under-specification rather than wasteful padding.

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

Completeness2/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 should explain the shape of the returned masked value, but it does not. For a four-parameter generator with no annotations, the definition leaves the agent guessing about output format and appropriate use.

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%, so length, parens, ellipsis, and maskChar are already documented in the schema. The description adds no syntax, defaults, or interaction details (e.g., how maskChar combines with length) beyond what the structured fields provide, so the baseline 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 states a specific verb and resource: it generates a random masked number, so an agent knows this is a fake-data generator rather than a validator. It does not differentiate itself from sibling generators such as finance-accountNumber or finance-creditCardNumber, nor does it clarify what 'masked' means in output terms.

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 guidance on when to use this tool, when to prefer a sibling generator, or what context (e.g., seeding test fixtures) makes it appropriate. The agent must infer usage entirely from the name and schema.

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