Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-verb

Returns a random verb, optionally filtered by expected length and fallback strategy, for generating fake text or test data in Faker workflows.

Instructions

Returns a random 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": "word-verb"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoThe expected length of the word or the options to use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it adds almost nothing beyond the one-line purpose. It does not say whether the result is seeded or truly random, how the 'strategy' fallback affects results, or what the returned shape is. The operation is inherently side-effect free, which lowers the stakes, but the disclosure gap remains.

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 front-loaded sentence with no filler, exactly as long as the stated purpose requires. It is efficient, though so terse that the remaining behavioral questions are simply left unanswered rather than addressed.

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 one optional, fully documented parameter, no output schema, and no annotations, the description covers the core action but omits return format and the effect of the length/strategy options. For a trivial random-word generator this is minimally sufficient but not complete.

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%, including documented min/max length and the enum strategy values, so the baseline is 3. The description contributes no additional meaning about the optional 'options' parameter, its nesting, or default behavior when it is omitted.

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 (returns) and resource (a random verb), which cleanly separates it from the sibling noun/adjective/adverb generators. It stops short of naming those siblings or contrasting behavior explicitly, but the single sentence leaves no ambiguity about what is produced.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives. Usage is strongly implied by the tool name and the word 'random', and for a zero-required-parameter generator the intended context is obvious, so this is adequate rather than generous.

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