Skip to main content
Glama

AutoTasker Hub — China Social Data API

random_user

Fake user profiles (gender, name, location, DOB, phone, avatar). $0.01 USDC.

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": "random_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
genderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add one genuinely useful behavioral fact beyond structured data: the $0.01 USDC cost per call, which lets an agent reason about spend. It does not disclose whether successive calls yield different profiles, any uniqueness guarantees, or failure behavior, so the disclosure is partial for a data-generation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact fragments, front-loaded with the payload description followed by the price tag; nothing is padded. The parenthetical field list is dense but each item tells the agent what it gets, so the terseness is efficient rather than under-specified here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple generator with no output schema and no annotations, the description covers the return shape and cost but omits the two input constraints (count ceiling, gender filter semantics). Those gaps matter because the schema itself carries no documentation, so an agent assembling a call has to guess at how the parameters behave.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the two parameters and does not. The listed fields (name, location, DOB, phone, avatar) are outputs, not inputs, and the description never says that gender narrows generation or that count defaults to 1 and caps at 10 – the most important constraints for correct invocation are left to the schema alone.

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?

The description names the resource precisely – fake user profiles – and enumerates the returned fields (gender, name, location, DOB, phone, avatar), so an agent can tell it is a synthetic-identity generator. It does not explicitly contrast with the sibling random_* generators, but the resource is specific enough that differentiation is implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says this is for test data, seeding, or mock users, and no exclusions or alternatives are named. The agent must infer applicability from the resource noun alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.