Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-jobDescriptor

Generates a random job descriptor for use as placeholder text in forms, UI mockups, and test data. Populate sample records without inventing job titles manually.

Instructions

Generates a random job descriptor.

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-jobDescriptor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one useful behavioral fact implicitly: output is random and therefore different on each call. Beyond that it says nothing about return shape, whether values are drawn from a fixed corpus, or whether repeated calls can collide.

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?

A single short sentence with no filler, and the core verb is front-loaded. Brevity is appropriate here, though the sentence is so thin that it edges toward under-specification rather than efficient communication.

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

Completeness2/5

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

The tool is simple and parameter-free, which lowers the bar, but with no output schema the description should indicate what a 'job descriptor' looks like (a single word such as 'Coordinator'/'Engineer' vs. a phrase) and how it differs from jobTitle. Neither is provided, so an agent cannot predict the returned value.

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, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. Nothing is missing on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ("Generates a random job descriptor"), so the action is understandable. However, it does not distinguish this from near-identical siblings such as person-jobTitle, person-jobArea, and person-jobType, leaving the agent unable to tell which job-related generator produces what. It is essentially a restatement of the name 'person-jobDescriptor' with no added scope.

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, no statement of prerequisites, and no mention of alternatives such as person-jobTitle or person-jobArea. The agent must infer entirely from the name that this is a filler-data generator and not a query tool.

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