Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-domainWord

Generates a random domain word for testing, mock data, or placeholder domain names.

Instructions

Generates a random domain word.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.7/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 of behavioral disclosure. It does not state whether this is a side-effect-free generator, whether output is a single token or a list, or whether results are unique or repeatable — only the bare action is asserted.

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

Conciseness3/5

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

The single short sentence is front-loaded and free of padding, which is good. But its brevity is achieved by omission rather than by efficiency — the wording is under-specified for a tool whose output shape is left entirely unexplained.

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?

With no output schema and no annotations, the description is the only source of truth about what comes back, and it does not say. For a zero-parameter generator with an ambiguous name, at least a note on return format (single word vs. full domain) is required for correct 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 tool takes zero parameters, so there are no parameter semantics to explain; the schema is empty and closed (additionalProperties: false). Baseline of 4 applies since there is nothing for the description to compensate for.

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 has a specific verb ("Generates") and a resource ("random domain word"), which is better than a tautology. However, "domain word" is ambiguous — it could mean a registrable domain, a label, or a word suitable for a domain name — and the description does nothing to distinguish this from siblings like internet-domainName and internet-domainSuffix. An agent cannot confidently separate the three.

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 the scenario this serves (e.g., placeholder data, test fixtures) and no mention of when to prefer internet-domainName or internet-domainSuffix instead. The agent must infer the choice purely from the names.

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