naija-faker-mcp

Generate a geographically consistent person

generate_consistent_person

Read-only

Generates a synthetic Nigerian person with coherent identity, address, state, and LGA. Filters title by ethnic group and returns language/region; optional language and gender inputs.

Instructions

Generates one synthetic person whose identity, address, state, and LGA are geographically coherent. The title is filtered to match the ethnic group. Also returns the language and region the record was drawn from. Accepts optional language and gender.

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
`language`	No	The person's language

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lga`	Yes
`email`	Yes
`phone`	Yes
`state`	Yes
`title`	Yes
`region`	Yes
`address`	Yes
`fullName`	Yes
`language`	Yes
`lastName`	Yes
`firstName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.0Sep 23, 2026

addedInput schema / properties / seed

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

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"
+}

changedOutput schema / required

Previous value: -[
-  "title",
-  "firstName",
-  "lastName",
-  "fullName",
-  "email",
-  "phone",
-  "address",
-  "state",
-  "lga"
-]New value: +[
+  "title",
+  "firstName",
+  "lastName",
+  "fullName",
+  "email",
+  "phone",
+  "address",
+  "state",
+  "lga",
+  "language",
+  "region"
+]

Changed5 schema fields changedv2.0.0Sep 16, 2026

changedInput schema / properties / gender / description

Previous value: -"The gender of the person data. 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 person data. 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"
+    },
+    "email": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "fullName": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "lga": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "phone": {
+      "type": "string"
+    },
+    "state": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "firstName",
+    "lastName",
+    "fullName",
+    "email",
+    "phone",
+    "address",
+    "state",
+    "lga"
+  ],
+  "type": "object"
+}

First observedv1.0.1Sep 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool read-only and non-destructive, lowering the bar. The description adds useful behavior: the title is filtered to the ethnic group, and the returned record includes the language and source region. It does not enumerate every generation rule, but the added facts are meaningful beyond the annotations.

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?

Three concise sentences with the core behavior front-loaded, followed by the distinctive title-filtering behavior and then the return/params. There is no filler or unnecessary repetition of schema details.

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?

The tool has an output schema to describe return values, annotations to cover safety, and all three parameters documented in the schema. The description adds the one thing the schema cannot express: what makes the person 'consistent' and how the title relates to ethnicity. Nothing needed to call it correctly is missing.

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 the baseline is 3. The description's phrase 'title is filtered to match the ethnic group' connects language to the title logic and adds a little meaning, but it does not explain seed behavior beyond the schema or add new detail for gender. The optionality of language and gender is already present in the schema.

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 opens with a specific verb and resource: 'Generates one synthetic person whose identity, address, state, and LGA are geographically coherent.' It also adds the distinguishing behavioral detail that the title is filtered to match the ethnic group, separating it from generic generate_person or generate_title. It clearly states the extra return value: 'Also returns the language and region the record was drawn from.'

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

Usage Guidelines4/5

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

The description gives clear context that this tool should be used when a single person record with geographically coherent fields and an ethnically matched title is needed. It does not explicitly name alternatives or say when not to use it, but the unique coherence property makes the intended use case apparent.

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