naija-faker-mcp

Generate a detailed person

generate_detailed_person

Read-only

Generate a synthetic Nigerian person with consistent identity, health, financial, kin, education, work, and vehicle records. Optionally specify gender and language (Hausa, Igbo, Yoruba).

Instructions

Generates one synthetic detailed person, including geographically consistent identity data plus health, financial, kin, education, work, and vehicle records. Accepts optional language and gender.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gender`	No	The person's gender
`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
`salary`	Yes
`address`	Yes
`vehicle`	Yes
`fullName`	Yes
`genotype`	Yes
`lastName`	Yes
`education`	Yes
`firstName`	Yes
`nextOfKin`	Yes
`bloodGroup`	Yes
`dateOfBirth`	Yes
`maritalStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.8/5.0

Behavior4/5

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

Annotations already signal a read-only, non-destructive operation, and the description adds value by revealing that generated data is geographically consistent and spans multiple domains. It also clarifies the tool produces exactly one person, not a batch. No contradiction with annotations is present.

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, dense sentence front-loads the core action ('Generates one synthetic detailed person') and then efficiently lists the included record categories and optional parameters. There is no filler or redundant elaboration.

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?

Given the output schema exists, annotations cover safety, and both parameters are fully documented in the schema, the description is largely sufficient. It conveys the singular output, breadth of included data, and geographic consistency, leaving only the sibling-selection guidance less explicit.

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 coverage is 100%, with both optional parameters already described and constrained by enums. The description only restates that language and gender are optional, adding no meaning beyond what the input schema already provides.

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'), a clear resource ('one synthetic detailed person'), and a concrete scope ('health, financial, kin, education, work, and vehicle records'). The word 'detailed' and the record list help distinguish it from simpler siblings like generate_person, though it does not explicitly name differences from generate_consistent_person.

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 implies this tool is for generating a comprehensive person profile with multiple bundled record types, which suggests when it would be preferred over a simpler generator. However, it never explicitly states when to use this tool instead of generate_person, generate_consistent_person, or generate_detailed_people, so the guidance remains inferential.

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