naija-faker-mcp

Generate a date of birth

generate_date_of_birth

Read-only

Generate a synthetic date of birth and corresponding age within optional minimum and maximum age limits.

Instructions

Generates a synthetic date of birth and age.

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": "generate_date_of_birth"
  }
}

Input Schema

Name	Required	Description	Default
`maxAge`	No
`minAge`	No

Output Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.0.0Sep 16, 2026

removedInput schema / properties / maxAge / description

Removed value: -"The maximum age of the date of birth"

addedInput schema / properties / maxAge / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / maxAge / minimum
```
Added value: +0
```

changedInput schema / properties / maxAge / type

Previous value: -"number"New value: +"integer"

removedInput schema / properties / minAge / description

Removed value: -"The minimum age of the date of birth"

addedInput schema / properties / minAge / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / minAge / minimum
```
Added value: +0
```

changedInput schema / properties / minAge / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "value": {}
+  },
+  "required": [
+    "value"
+  ],
+  "type": "object"
+}

First observedv1.0.1Sep 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context: 'synthetic' indicates non-real data, and 'and age' shows that age is also generated. It does not explain randomness, how age is calculated relative to the current date, or how min/max age constraints affect the result.

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?

The description is one short, front-loaded sentence with every word earning its place. It avoids repeating the schema or annotations and wastes no space. This is an appropriate size for a tool with only two optional parameters and an output schema.

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?

The tool is simple, and the output schema plus annotations cover return structure and safety, so the description need not explain those. However, with zero schema descriptions and no usage guidance, the semantics of minAge/maxAge and the decision among sibling tools remain unresolved. It is minimally usable but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description bears the burden of explaining minAge and maxAge, but it does not mention them at all. An agent must infer from property names that these parameters bound the generated age. No defaults, inclusiveness, or behavior for invalid combinations are provided.

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 uses a specific verb ('Generates') and names a concrete resource ('synthetic date of birth and age'), which clearly distinguishes it from sibling tools like generate_name or generate_phone_number. It is not a pure tautology because it adds 'synthetic' and the fact that age is also produced. It does not, however, clarify how it relates to generate_person, which might also produce a date of birth.

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 about when to use this tool versus the many sibling tools. It does not mention alternatives such as generate_person or generate_detailed_person for full profiles, nor does it state when a standalone date of birth is appropriate. The agent is left to infer selection from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.