naija-faker-mcp

Generate a detailed person

generate_detailed_person

Read-only

Generate a detailed synthetic Nigerian person with consistent identity, health, financial, kin, education, work, and vehicle records, all derived from a single coherent profile.

Instructions

Generates one synthetic detailed person, including geographically consistent identity data plus health, financial, kin, education, work, and vehicle records. Every field is derived from one identity, so graduation follows birth and employment follows graduation. Defaults to ages 22-65; widen the range with minAge and maxAge, and education is null for anyone too young to have finished a qualification.

Input Schema

TableJSON Schema

Name	Required	Description
`seed`	No	Seed for reproducible output; the same seed returns the same record
`gender`	No	The person's gender
`maxAge`	No	Oldest age to generate
`minAge`	No	Youngest age to generate
`language`	No	The person's language

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lga`	Yes
`work`	Yes
`email`	Yes
`phone`	Yes
`state`	Yes
`title`	Yes
`region`	Yes
`salary`	Yes
`address`	Yes
`vehicle`	Yes
`fullName`	Yes
`genotype`	Yes
`language`	Yes
`lastName`	Yes
`education`	Yes
`firstName`	Yes
`nextOfKin`	Yes
`bloodGroup`	Yes
`dateOfBirth`	Yes
`maritalStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.1.0Sep 23, 2026

addedInput schema / properties / maxAge

Added value: +{
+  "description": "Oldest age to generate",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / minAge

Added value: +{
+  "description": "Youngest age to generate",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / seed

Added value: +{
+  "description": "Seed for reproducible output; the same seed returns the same record",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedOutput schema / properties / education / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / education / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "abbreviation": {
+        "type": "string"
+      },
+      "course": {
+        "type": "string"
+      },
+      "degree": {
+        "type": "string"
+      },
+      "discipline": {
+        "type": "string"
+      },
+      "graduationYear": {
+        "type": "number"
+      },
+      "university": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "university",
+      "abbreviation",
+      "degree",
+      "discipline",
+      "course",
+      "graduationYear"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / education / properties

Removed value: -{
-  "abbreviation": {
-    "type": "string"
-  },
-  "course": {
-    "type": "string"
-  },
-  "degree": {
-    "type": "string"
-  },
-  "graduationYear": {
-    "type": "number"
-  },
-  "university": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / education / required

Removed value: -[
-  "university",
-  "abbreviation",
-  "degree",
-  "course",
-  "graduationYear"
-]

removedOutput schema / properties / education / type
```
Removed value: -"object"
```

addedOutput schema / properties / language

Added value: +{
+  "enum": [
+    "hausa",
+    "igbo",
+    "yoruba"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / region

Added value: +{
+  "enum": [
+    "east",
+    "west",
+    "north",
+    "south"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / work / properties / level

Added value: +{
+  "enum": [
+    "entry",
+    "mid",
+    "executive",
+    "senior"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / work / properties / yearsOfExperience
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / work / required

Previous value: -[
-  "company",
-  "position",
-  "industry",
-  "startYear"
-]New value: +[
+  "company",
+  "position",
+  "industry",
+  "startYear",
+  "yearsOfExperience",
+  "level"
+]

changedOutput schema / required

Previous value: -[
-  "title",
-  "firstName",
-  "lastName",
-  "fullName",
-  "email",
-  "phone",
-  "address",
-  "state",
-  "lga",
-  "dateOfBirth",
-  "maritalStatus",
-  "bloodGroup",
-  "genotype",
-  "salary",
-  "nextOfKin",
-  "education",
-  "work",
-  "vehicle"
-]New value: +[
+  "title",
+  "firstName",
+  "lastName",
+  "fullName",
+  "email",
+  "phone",
+  "address",
+  "state",
+  "lga",
+  "language",
+  "region",
+  "dateOfBirth",
+  "maritalStatus",
+  "bloodGroup",
+  "genotype",
+  "salary",
+  "nextOfKin",
+  "education",
+  "work",
+  "vehicle"
+]

Changed5 schema fields changedv2.0.0Sep 16, 2026

changedInput schema / properties / gender / description

Previous value: -"The gender of the detailed person. The accepted gender values are male and female"New value: +"The person's gender"

addedInput schema / properties / gender / enum
```
Added value: +[
+  "male",
+  "female"
+]
```

changedInput schema / properties / language / description

Previous value: -"The language of the detailed person. The available languages are Hausa, Igbo and Yoruba"New value: +"The person's language"

addedInput schema / properties / language / enum

Added value: +[
+  "hausa",
+  "igbo",
+  "yoruba"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "bloodGroup": {
+      "type": "string"
+    },
+    "dateOfBirth": {
+      "additionalProperties": false,
+      "properties": {
+        "age": {
+          "type": "number"
+        },
+        "date": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "date",
+        "age"
+      ],
+      "type": "object"
+    },
+    "education": {
+      "additionalProperties": false,
+      "properties": {
+        "abbreviation": {
+          "type": "string"
+        },
+        "course": {
+          "type": "string"
+        },
+        "degree": {
+          "type": "string"
+        },
+        "graduationYear": {
+          "type": "number"
+        },
+        "university": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "university",
+        "abbreviation",
+        "degree",
+        "course",
+        "graduationYear"
+      ],
+      "type": "object"
+    },
+    "email": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "fullName": {
+      "type": "string"
+    },
+    "genotype": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "lga": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "maritalStatus": {
+      "type": "string"
+    },
+    "nextOfKin": {
+      "additionalProperties": false,
+      "properties": {
+        "address": {
+          "type": "string"
+        },
+        "fullName": {
+          "type": "string"
+        },
+        "phone": {
+          "type": "string"
+        },
+        "relationship": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "fullName",
+        "relationship",
+        "phone",
+        "address"
+      ],
+      "type": "object"
+    },
+    "phone": {
+      "type": "string"
+    },
+    "salary": {
+      "additionalProperties": false,
+      "properties": {
+        "amount": {
+          "type": "number"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "frequency": {
+          "type": "string"
+        },
+        "level": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "currency",
+        "level",
+        "frequency"
+      ],
+      "type": "object"
+    },
+    "state": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "vehicle": {
+      "additionalProperties": false,
+      "properties": {
+        "color": {
+          "type": "string"
+        },
+        "licensePlate": {
+          "type": "string"
+        },
+        "make": {
+          "type": "string"
+        },
+        "model": {
+          "type": "string"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "licensePlate",
+        "make",
+        "model",
+        "year",
+        "color"
+      ],
+      "type": "object"
+    },
+    "work": {
+      "additionalProperties": false,
+      "properties": {
+        "company": {
+          "type": "string"
+        },
+        "industry": {
+          "type": "string"
+        },
+        "position": {
+          "type": "string"
+        },
+        "startYear": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "company",
+        "position",
+        "industry",
+        "startYear"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "title",
+    "firstName",
+    "lastName",
+    "fullName",
+    "email",
+    "phone",
+    "address",
+    "state",
+    "lga",
+    "dateOfBirth",
+    "maritalStatus",
+    "bloodGroup",
+    "genotype",
+    "salary",
+    "nextOfKin",
+    "education",
+    "work",
+    "vehicle"
+  ],
+  "type": "object"
+}

First observedv1.0.1Sep 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds valuable behavioral context beyond the annotations: it explains that all fields are derived from one identity, ensuring internal consistency (graduation follows birth, employment follows graduation), and discloses the age-range default and the edge case where education is null. This goes beyond the readOnlyHint and destructiveHint annotations, which only cover safety. However, it does not mention seed reproducibility or output format, though those are covered by the schema.

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 two sentences, front-loaded with the core purpose and scope, then adding the age/education nuance. There is no fluff or redundancy; every sentence earns its place. It is concise yet informative.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential aspects: what the tool does, the consistency guarantee, and the age/education behavior. The output schema handles the return structure, and annotations handle safety. The only notable gap is the lack of explicit differentiation from sibling tools, which is partially covered by the name and content. Overall, it is complete for an agent to invoke it correctly, with minor room for improvement in routing guidance.

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?

Schema description coverage is 100%, so all five parameters are documented in the schema itself. The description adds extra meaning by explaining the effect of minAge and maxAge (default 22-65) and the condition under which education is null, which is not present in the schema. This enriches parameter understanding beyond the schema's field-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Generates' and the resource 'one synthetic detailed person', and enumerates the domains covered (health, financial, kin, education, work, vehicle). It distinguishes itself from simpler siblings like generate_person by emphasizing 'detailed' and 'geographically consistent', which is a unique feature not present in other generators.

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 provides some usage context (default age range, how to widen it, and the education-null edge case) but does not explicitly state when to choose this tool over alternatives such as generate_person or generate_consistent_person. It implies usage through the 'detailed' descriptor but lacks explicit exclusion or alternative guidance, leaving the selection partially to inference.

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