Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

hacker-ingverb

Returns a random hacker/IT verb ending in -ing to represent continuous actions like hacking, useful for fake data generation and testing.

Instructions

Returns a random hacker/IT verb for continuous actions (en: ing suffix; e.g. hacking).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the key behavioral trait, randomness ('Returns a random'), and the deterministic output shape via the example 'hacking'. It does not state that it is read-only with no side effects, whether output is lowercase, or whether results repeat.

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?

A single compact sentence with the verb of action front-loaded and the clarifying parenthetical plus example immediately after. Nothing is wasted and nothing essential is buried.

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-parameter random-value generator with no output schema and no annotations, the description covers what it returns and in what form, which is sufficient to invoke it correctly. A brief note on output casing or non-uniqueness would close the remaining gap.

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 the baseline is 4; there is no parameter meaning to convey. The description correctly implies no input is needed by describing the call as a bare retrieval.

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?

States a specific verb and resource: it returns a random hacker/IT verb. The parenthetical '(en: ing suffix; e.g. hacking)' pins down the exact grammatical form, which is what separates it from the sibling hacker-verb, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'for continuous actions', which hints at when this form is preferred over a base-form verb. There is no explicit statement of when to choose this over hacker-verb or other word-generation siblings, and no exclusions.

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