Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

hacker-adjective

Generates a random hacker or IT adjective to seed fake data, test fixtures, and placeholder content.

Instructions

Returns a random hacker/IT adjective.

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

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?

No annotations are supplied, so the description carries the behavioral burden. It does disclose the most important trait: the return value is random (non-deterministic), and the absence of side effects is implied by 'Returns.' For a zero-parameter read-only generator that is roughly adequate, but nothing is said about uniqueness, format, or whether repeated calls can repeat values.

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?

One short sentence with the resource ('random hacker/IT adjective') front-loaded and no filler. It is appropriately sized for the tool's triviality, though it is so terse that it leaves the usage and output questions entirely unaddressed.

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?

With zero parameters, no annotations, and no output schema, the description is the only documentation an agent gets. Saying it returns a random adjective covers the core, but the return shape (plain string? list?) and any intended use case are left implicit.

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 for the description to add. The baseline for a parameterless tool applies, with no gap to compensate for.

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+resource: 'Returns a random hacker/IT adjective.' The word 'adjective' plus the 'hacker/IT' domain distinguishes it from siblings like hacker-noun, hacker-verb, and word-adjective without needing the schema. It stops short of explicitly naming those siblings as alternatives, which is why it is not a 5.

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 at all, and no sibling alternatives are named. An agent can infer that this is a filler/mock-data generator, but the description never says so, nor does it indicate how it differs from the other random-word generators in the catalog.

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