Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-domainSuffix

Returns a random domain suffix for generating fake internet data such as URLs and email addresses. Use it to populate test fixtures and mock records with realistic top-level domains.

Instructions

Returns a random domain suffix.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does carry the full behavioral burden, and it does disclose the one important trait: output is random, so results are non-deterministic and not repeatable. It does not say whether the suffix includes a leading dot (".com" vs "com") or give an example, which is a real ambiguity for a generator tool.

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 zero wasted words, front-loaded with the verb and resource. It is efficiently sized for a trivial generator, though it leaves room for one clarifying clause about output format.

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 no-parameter random generator with no annotations and no output schema, the definition covers the essentials but omits the return format detail that matters most here: whether the value arrives with or without a leading dot. Nothing about side effects needs stating since a random string producer is inherently safe.

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 is no parameter meaning to convey; the baseline of 4 applies. The empty schema with additionalProperties=false is self-documenting.

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?

"Returns a random domain suffix" gives a specific verb (returns) and a specific resource (domain suffix), which an agent can distinguish from a full-domain generator like internet-domainName. It stops short of explicitly contrasting itself with the nearest sibling, but the resource noun is precise enough to select correctly.

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?

The description offers no guidance on when to reach for this tool versus generating a whole domain name or other internet-* generators. There is no stated context, prerequisite, or exclusion, so usage must be inferred from the tool name alone.

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