naija-faker-mcp

Generate detailed people

generate_detailed_people

Read-only

Generate synthetic profiles with Nigerian identity, health, financial, education, work, kin, and vehicle data. Specify count, gender, and language to create realistic test data for applications.

Instructions

Generates an array of synthetic detailed people. Each record includes geographically consistent identity data plus health, financial, kin, education, work, and vehicle records. Returns one record by default.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	The number of people to generate
`gender`	No	The person's gender
`language`	No	The person's language

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.0.0Sep 16, 2026

changedInput schema / properties / count / description

Previous value: -"The number of detailed people to generate"New value: +"The number of people to generate"

addedInput schema / properties / count / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / count / minimum
```
Added value: +1
```

changedInput schema / properties / count / type

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

changedInput schema / properties / gender / description

Previous value: -"The gender of the detailed people. 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 people. 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": {
+    "items": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedv1.0.1Sep 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value by stating 'Returns one record by default' and specifying the geographic consistency and comprehensive record composition, which clarifies behavior beyond the schema. This is strong disclosure given the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no redundant content. It front-loads the primary purpose and key detail (array, detailed), then adds default behavior and data breadth. Every sentence earns its place—efficient and well-structured.

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

Completeness5/5

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

Given the tool has a rich output schema (not shown but indicated as present), the description doesn't need to enumerate return fields. It clearly explains the tool's scope, default behavior, and data categories, which is sufficient for agents to select and invoke it correctly. The complexity is high but well-covered by description plus annotations.

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%, so each parameter (count, gender, language) is already documented with types and descriptions. The description adds little beyond the schema—it doesn't explain how gender/language affect the records or what default values are used. At 100% coverage, baseline 3 is appropriate.

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 clearly states the tool generates synthetic detailed people, specifying the resource ('array of synthetic detailed people') and the breadth of data included (identity plus health, financial, etc.). It distinguishes from generic people generators by emphasizing 'detailed' and listing covered domains, though it doesn't explicitly name a sibling like generate_detailed_person or generate_people, so it's clear but not fully distinguishing.

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 usage for generating bulk detailed records, but does not explicitly state when to prefer this over siblings like generate_detailed_person (single) or generate_consistent_people (consistency-specific). No exclusions or alternatives are mentioned, so context is only partially implied.

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