Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-birthdate

Generates a random birthdate, defaulting to ages 18–80, and lets you set age or year ranges to create targeted test data.

Instructions

Returns a random birthdate. By default, the birthdate is generated for an adult between 18 and 80 years old. But you can customize the 'age' range or the 'year' range to generate a more specific birthdate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "union": "<union>"
    },
    "name": "date-birthdate"
  }
}

Input Schema

NameRequiredDescriptionDefault
unionYes

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 important default range (18-80, adult) and the randomized nature of the output, which is genuinely useful behavioral context. It omits what date format is returned, whether refDate affects age-mode calculation, and any range validation behavior.

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?

Three short sentences, front-loaded with the core behavior, then the default, then the customization option. Nothing is redundant, though the final sentence could be tightened by naming the exact parameters instead of quoting field names.

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 single-parameter tool with a union schema and no output schema, the description covers purpose, default range, and the two customization modes. It leaves refDate unexplained and gives no indication of output format, which is a meaningful gap given the nested anyOf structure an agent must navigate.

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 0%, so the description must compensate. It partially does by naming the two modes ('age' range and 'year' range), which map to the union's mode const values, and by establishing that one mode is the default. However, it never mentions refDate, which the schema itself only documents inline, and it does not clarify min/max units or inclusivity.

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 opens with a specific verb and resource: 'Returns a random birthdate.' That is clearly distinct from siblings like date-anytime or date-past, which produce arbitrary dates rather than birthdates. It does not name any sibling explicitly, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the default behavior (an adult aged 18-80) and states that the age or year range can be customized for a more specific result. This is useful usage context, but there is no explicit guidance on when to prefer this tool over the other date generators, and no mention of the interaction with refDate.

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