Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-sexType

Generates a random sex type value for use in parameters and conditional logic.

Instructions

Returns a random sex type. The SexType is intended to be used in parameters and conditions.

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": "person-sexType"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does disclose the key trait — the value is random and represents a type rather than a specific person's data — but says nothing about the set of possible values, determinism per call, or what the returned shape is.

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, front-loaded with what the tool returns and followed by the one piece of context an agent needs about its intended use. No filler or redundant restatement of the title.

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 trivial zero-argument generator this is nearly sufficient, but with no output schema and no annotations the description should say what the return value looks like (a string from a fixed vocabulary) to be fully actionable. As written, an agent knows the concept but not the output form.

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 tool takes zero parameters and the schema confirms an empty object with additionalProperties false, so there is nothing for the description to explain. Baseline 4 applies; the description correctly avoids inventing parameter guidance.

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 specific verb and resource: 'Returns a random sex type,' so an agent knows it produces a value rather than querying data. It does not distinguish itself from the similarly named sibling person-sex or person-gender, leaving ambiguity about which one to call.

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 clause 'intended to be used in parameters and conditions' implies this is a schema/type helper for building other inputs, which is genuine usage context. However, it gives no explicit when-to-use versus person-sex or person-gender, and no exclusions or prerequisites.

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

Deploy Server

Other Tools