Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

hacker-verb

Returns a random hacker or IT verb for use in generated text, sample data, and filler content. Call it to get a single verb without parameters.

Instructions

Returns a random hacker/IT verb.

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

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key non-obvious trait — output is random/nondeterministic — but says nothing about whether the result is a single word or a phrase, whether it may repeat across calls, or whether there is any casing/punctuation convention.

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 short sentence, front-loaded with the verb, nothing redundant. Perfectly sized for a trivial generator.

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 zero-parameter, no-output-schema random generator, the description covers what the tool produces. Only minor gaps remain: no sample value or format hint to set expectations about word count or casing.

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 applies. The empty schema is consistent with the description, which implies no input is needed.

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: 'Returns a random hacker/IT verb.' The agent knows exactly what comes back. It does not name or distinguish itself from siblings like hacker-noun, hacker-ingverb, or word-verb, though the name-plus-description pairing makes the domain clear.

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 implied by the domain — grab a hacker-flavored verb when generating hacker-style text — but the description gives no explicit when-to-use guidance and no pointer to the noun/adjective/phrase siblings or to word-verb for ordinary verbs. Adequate but leaves routing to the agent.

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