Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-password

Generate random password-like strings with customizable length, prefix, pattern, and memorable options for testing, mock data, or placeholder credentials.

Instructions

Generates a random password-like string.

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": "internet-password"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe length of the password to generate.
prefixNoThe prefix to use.
patternNoThe pattern that all chars should match.
memorableNoWhether the generated password should be memorable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/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 behavioral burden and discloses almost nothing. It does not state that the output is not cryptographically secure, whether results are deterministic per seed, what the default length is, or how 'memorable' alters the output. For a generator with zero annotation coverage, this is a substantial gap.

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 action is front-loaded. It is concise to the point of under-specification, but nothing in it is wasted or redundant.

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?

Four optional parameters, no output schema, and no annotations mean the description must do the explanatory work, and it does not. An agent still cannot tell whether the result is safe for real use, what the defaults are, or how the pattern and memorable options interact.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented in the schema, which sets the baseline at 3. The description adds no meaning beyond the schema — it never explains what 'memorable' does in practice, what format 'pattern' expects, or what length is used when omitted.

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 states a specific verb and resource: 'Generates a random password-like string.' An agent can tell this produces a string, not an object or a lookup. However, the hedge 'password-like' is the only signal that this is synthetic test data rather than a real credential generator, and no sibling (e.g. internet-jwt, internet-userAgent) is distinguished.

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 that this is intended for fixture/seed data rather than real account security, and no mention of alternatives. The agent must infer the use case entirely from the tool name.

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