Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

hacker-phrase

Generates a random hacker or IT-themed phrase, giving developers ready-made text for test fixtures, mock data, and playful placeholder content.

Instructions

Generates a random hacker/IT phrase.

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": "hacker-phrase"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/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 load: it does disclose that output is random and that it is a phrase rather than a single token, which is the key behavioral trait for a zero-parameter generator. It says nothing about determinism, seeding, or the shape/length of the returned phrase.

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, front-loaded with the action and output type. Nothing is wasted, though nothing is elaborated either.

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

Completeness4/5

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

For a trivial, zero-argument random-value generator with no annotations or output schema, this one sentence is close to sufficient. The only real gap is that the format of the returned phrase is never described.

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 no parameters and the schema is an empty object, so there is no parameter meaning to add. Baseline of 4 applies.

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 hacker/IT phrase'), which is clearly distinct from a single-word generator like hacker-noun or hacker-verb listed among the siblings. It stops short of explicitly contrasting itself with those siblings, leaving the agent to infer the granularity difference.

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 or when-not-to-use guidance and no mention of the part-generator siblings (hacker-noun, hacker-verb, hacker-adjective). The only implicit cue is the word 'phrase', which the agent must interpret on its own.

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