naija-faker-mcp

Generate a geographically consistent person

generate_consistent_person

Read-only

Create a synthetic Nigerian person whose identity, address, state, and LGA are geographically aligned. Optionally select language and gender to match ethnic groups.

Instructions

Generates one synthetic person whose identity, address, state, and LGA are geographically coherent. 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
`email`	Yes
`phone`	Yes
`state`	Yes
`title`	Yes
`address`	Yes
`fullName`	Yes
`lastName`	Yes
`firstName`	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 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.1/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description adds that the generated person's identity, address, state, and LGA are mutually coherent, and that language and gender are optional. No contradiction with 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?

Two short sentences with the main purpose front-loaded and no filler. Every word earns its place.

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?

For a generator with only two optional enum parameters, an output schema, and safety annotations, the description is complete enough for an agent to understand and invoke it correctly.

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 description coverage is 100% and both parameters have enums and descriptions. The description only repeats that language and gender are optional, which is already visible from required:0. It adds no extra meaning about how these params affect coherence.

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?

States a specific verb ('Generates'), a single synthetic person, and the key property: identity, address, state, and LGA are geographically coherent. This clearly differentiates it from generic generate_person and from the plural generate_consistent_people.

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 use when geographic coherence matters, but it does not explicitly name alternatives or state when not to use this tool. With many sibling generation tools, explicit routing would be stronger.

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