naija-faker-mcp

Generate fake people

generate_people

Read-only

Generate an array of synthetic Nigerian person records, with an optional count to return more than the default 10.

Instructions

Generates an array of basic composite synthetic person records. Accepts an optional positive count and returns 10 records by default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	The number of people to generate

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.0Sep 16, 2026

changedInput schema / properties / count / description

Previous value: -"The number of persons to be generated as part of the people list"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"

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"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "firstName",
+          "lastName",
+          "fullName",
+          "email",
+          "phone",
+          "address"
+        ],
+        "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 declare readOnlyHint and destructiveHint, so the description only needs to add behavioral context. It adds useful details: the result is an array, records are basic and composite/synthetic, count is optional, and 10 is the default. This goes beyond the annotation baseline without contradicting it.

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, tightly written sentence that front-loads the core behavior and then adds the key default behavior. No filler or redundancy.

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?

With a single optional parameter, clear annotations, and an output schema present, the description covers the essential calling contract: optional count and default output size. It could name sibling alternatives, but that is more a usage-guidance gap than a completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents count as an integer with a minimum of 1, and schema coverage is 100%. The description adds meaning by stating the count is optional and that the default is 10 records, which the schema does not convey.

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?

States a clear verb and resource: it generates an array of synthetic person records. The words 'array' and 'basic composite' implicitly distinguish it from singular, detailed, and consistent person generators, though it does not name a sibling explicitly.

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 multiple basic synthetic person records are needed, and the default count of 10 hints at batch generation. However, it gives no explicit guidance about when to choose this over generate_person, generate_consistent_people, or generate_detailed_people.

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