Skip to main content
Glama

Synthetic Data — Random User

by ai.saifs
OverviewDiscussionsAdmin

Server Details

Generate synthetic random user data for testing, demos, and development without using real persona.

Ownership verified
Status
Healthy
Uptime
99.7% over 56 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: one generates synthetic user profiles and the other saves feedback. There is no overlap or ambiguity between them.

Naming Consistency4/5

Both names are lowercase and noun-like ('feedback', 'random_users'), which is reasonably consistent. The only minor deviation is that one is a single word while the other uses an underscore.

Tool Count3/5

Two tools is on the thin side for a server, and only one of them actually serves the stated synthetic-data purpose. It is not absurdly small, but it feels slightly under-scoped.

Completeness4/5

The random_users tool covers the core need of generating fake user profiles with configurable count and pro status. Minor extras like locale or seed options could be missing, but no major workflow dead-end is apparent.

Available Tools

1 tool
random_usersGenerate Random UsersA
Read-only
Inspect

Generate synthetic / fake user profiles via the MwVideos random_users API (POST /mwvideos/api/random_users). Returns name, gender, location, email, login, dob, phone, picture, and nat. Use when the user asks for random users, fake people, sample contacts, demo personas, UI fixtures, or test profiles. Pass results for how many profiles (default 1, minimum 1) and isPro as 0 or 1 when relevant (default 0). Authenticated user_id is injected server-side — do not invent profiles; always call this tool. These are FAKE people for demos and testing, not real PII.

ParametersJSON Schema
NameRequiredDescriptionDefault
isProNoPro flag passed through to the upstream API (0 or 1).
resultsNoNumber of random user profiles to generate. Must be an integer >= 1.

Output Schema

ParametersJSON Schema
NameRequiredDescription
infoNo
statusYes1 = success, 0 = error
messageNo
resultsYesList of synthetic user profiles from the upstream API.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that 'Authenticated user_id is injected server-side' and warns that these are 'FAKE people for demos and testing, not real PII.' This adds meaningful context about the tool's behavior and data nature.

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 efficiently organized: purpose first, then usage, parameters, and a final caveat. Every sentence contributes, and the length is appropriate for the tool's complexity.

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 description covers purpose, usage, parameters, authentication context, and data nature, while the output schema handles return values. No significant gaps remain for effective tool invocation.

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 already documents both parameters with descriptions and examples, achieving 100% coverage. The description adds usage nuance, such as 'results' default/minimum and 'isPro' as 0 or 1 'when relevant', which enhances understanding beyond 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 clearly states the tool's function: 'Generate synthetic / fake user profiles' and references the specific API endpoint (POST /mwvideos/api/random_users). It also lists the returned fields, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Provides explicit use cases: 'when the user asks for random users, fake people, sample contacts, demo personas, UI fixtures, or test profiles.' It also instructs to 'always call this tool' rather than inventing profiles, giving clear guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Removedfeedback
    • Changedrandom_users2 fields changed
      • removedOutput schema / properties / feedback_prompt
        Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": false,
-      "properties": {
-        "message": {
-          "type": "string"
-        },
-        "must_ask": {
-          "type": "boolean"
-        },
-        "output_count": {
-          "type": "integer"
-        },
-        "reactions": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "emoji": {
-                "type": "string"
-              },
-              "label": {
-                "type": "string"
-              },
-              "value": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "value",
-              "emoji",
-              "label"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "ready": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "ready"
-      ],
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
      • removedOutput schema / properties / output_count
        Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "MCP runs for this user (one user question = one run). Feedback is due on the 3rd, 6th, 9th, … run."
-}
  2. 2 tool updates
    • Changedfeedback1 field changed
      • changedInput schema / properties / feedback / description
        Previous value: -"Optional short comment from the user."New value: +"Optional short comment from the user. If omitted or empty, the server stores this MCP's name."
    • Changedrandom_users1 field changed
      • changedOutput schema / properties / output_count / description
        Previous value: -"Successful random_users outputs since last feedback. Feedback is due at 3 and stays due until it is saved."New value: +"MCP runs for this user (one user question = one run). Feedback is due on the 3rd, 6th, 9th, … run."
  3. 1 tool update
    • Changedrandom_users2 fields changed
      • changedOutput schema / properties / feedback_prompt / anyOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "message": {
-        "type": "string"
-      },
-      "output_count": {
-        "type": "integer"
-      },
-      "reactions": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "emoji": {
-              "type": "string"
-            },
-            "label": {
-              "type": "string"
-            },
-            "value": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "value",
-            "emoji",
-            "label"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "ready": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "ready"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "message": {
+        "type": "string"
+      },
+      "must_ask": {
+        "type": "boolean"
+      },
+      "output_count": {
+        "type": "integer"
+      },
+      "reactions": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "emoji": {
+              "type": "string"
+            },
+            "label": {
+              "type": "string"
+            },
+            "value": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "value",
+            "emoji",
+            "label"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "ready": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "ready"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
      • changedOutput schema / properties / output_count / description
        Previous value: -"Successful random_users outputs since last feedback. Feedback is collected after every 3."New value: +"Successful random_users outputs since last feedback. Feedback is due at 3 and stays due until it is saved."
  4. 1 tool update
    • Changedrandom_users1 field changed
      • changedOutput schema / properties / output_count / description
        Previous value: -"Successful random_users outputs in this MCP session. Feedback is collected after 3."New value: +"Successful random_users outputs since last feedback. Feedback is collected after every 3."
  5. 2 tool updates
    • Addedfeedback
    • Changedrandom_users2 fields changed
      • addedOutput schema / properties / feedback_prompt
        Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "message": {
+          "type": "string"
+        },
+        "output_count": {
+          "type": "integer"
+        },
+        "reactions": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "emoji": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "value",
+              "emoji",
+              "label"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "ready": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "ready"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
      • addedOutput schema / properties / output_count
        Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Successful random_users outputs in this MCP session. Feedback is collected after 3."
+}
  6. 1 tool update
    • First observedrandom_users

Related MCP Connectors

Related MCP Servers

  • Faker MCP Server

    funsjanssen
    A
    license
    B
    quality
    D
    maintenance
    Generates realistic mock data using Faker.js for database seeding, API testing, and development environments. Supports person/company data, custom patterns, multi-locale generation, and structured datasets with referential integrity.
    4
    84 npm
    7
    MIT

  • FauxGen MCP

    LazyInvestor
    A
    license
    B
    quality
    A
    maintenance
    Enables Cursor, Claude, Windsurf, and other compatible hosts to generate fictional identities, addresses, phone numbers, emails, companies, device/network details, and checksum-valid test payment data across 66 countries. It also provides deep links to visual web tools plus prompts and resources for seeding test users.
    4
    17
    106 npm
    MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources