naija-faker-mcp

Generate geographically consistent people

generate_consistent_people

Read-only

Generate synthetic Nigerian people with matching identity, address, state, and LGA fields. Specify count, gender, or language for consistent test data.

Instructions

Generates an array of synthetic people with geographically coherent identity, address, state, and LGA fields. Accepts an optional positive count and returns 10 records by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_consistent_people"
  }
}

Input Schema

Name	Required	Description
`seed`	No	Seed for reproducible output; the same seed returns the same record
`count`	No	The number of people to generate
`gender`	No	The person's gender
`language`	No	The person's language

Output Schema

Name	Required	Description	Default
`items`	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 / items / items / properties / language

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

addedOutput schema / properties / items / items / properties / region

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

changedOutput schema / properties / items / items / 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"
+]

Changed8 schema fields changedv2.0.0Sep 16, 2026

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 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": {
+    "items": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "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?

With readOnlyHint and destructiveHint already provided by annotations, the description adds meaningful context: output is an array, default is 10 records, count is optional, and fields are geographically coherent. This exceeds what annotations alone communicate, though it does not detail randomness or reproducibility beyond 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?

Two sentences, front-loaded with the core purpose and followed by the default-count behavior. There is no filler or repetition of schema details.

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 an output schema exists, a 100%-covered input schema, and safety annotations, the description is adequate for correct invocation. It lacks an explicit mention of seed reproducibility, but that is already in the schema, so nothing critical 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 description coverage is 100%, so the schema already documents seed, count, gender, and language. The description adds only the default count behavior ('returns 10 records'), which is minor. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 uses a specific verb ('Generates') and resource ('an array of synthetic people') with a clear qualifier ('geographically coherent identity, address, state, and LGA fields'). This distinguishes it from sibling tools like generate_people (generic) and generate_consistent_person (singular rather than array).

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: use this tool when multiple synthetic people with geographically coherent fields are needed, and it notes the default count behavior. It does not explicitly name alternatives or exclusions relative to siblings, so it stops short of a 5.

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