Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-url

Generates random HTTP or HTTPS URLs with selectable protocol and optional trailing slash for mock data, API testing, or filling sample internet records.

Instructions

Generates a random http(s) url.

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

Input Schema

NameRequiredDescriptionDefault
protocolNoThe protocol to use.
appendSlashNoWhether to append a slash to the end of the url (path).

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?

No annotations are supplied, so the description carries the full behavioral burden. 'Random' is the single most important trait here — it tells the agent output is non-deterministic — but nothing is said about whether output is a plain string, whether a path/query is included, or whether uniqueness is guaranteed. Adequate, not rich.

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?

One sentence, front-loaded with the verb and resource, with no filler or redundancy. Nothing could be removed without losing meaning.

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?

This is a simple two-optional-parameter generator with no output schema, so the bar is low. Still, the description never states the shape of the returned value — a bare URL string versus an object — which is the main thing an agent needs before consuming the result.

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 both 'protocol' (enum-documented) and 'appendSlash' are already explained in structured data. The description adds no syntax or default detail beyond what the schema provides, which is the expected baseline-3 outcome for a fully documented schema.

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 gives a specific verb and resource: 'Generates a random http(s) url.' An agent can immediately tell this produces URL strings, and the parenthetical '(s)' hints at the protocol parameter. It stops short of distinguishing itself from nearby generators like internet-domainName or internet-protocol, but the resource is concrete enough to act on.

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 guidance on when to use this versus alternatives, no prerequisites, and no exclusions. The agent must infer from the sibling list whether it wants a full URL or a component generator such as internet-domainName or internet-protocol.

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