Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-sample

Returns a random word from categories like adjective, noun, or verb, with optional length constraints and fallback strategies for handling no length matches.

Instructions

Returns a random word, that can be an adjective, adverb, conjunction, interjection, noun, preposition, or 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-sample"
  }
}

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
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the key behavioral trait — that the result is random and drawn from a multi-part-of-speech pool — but says nothing about failure behavior when a length constraint cannot be satisfied, whether the call is side-effect free, or how the random selection is seeded.

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 the core behavior stated first and the enumeration of word types as supporting detail. The parts-of-speech list is somewhat long but earns its place by defining the result pool.

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 one-optional-parameter tool with no output schema, the description covers what the tool returns and the space of possible results. The only gap is behavior under length constraints, which the schema's strategy enum largely addresses on its own.

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 per-field descriptions for min/max length and the strategy enum, so the baseline is 3. The description adds nothing about the optional length/options parameter, but the schema already documents it thoroughly.

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 ('Returns a random word') and enumerates the possible parts of speech, which implicitly distinguishes it from the single-type siblings like word-noun or word-adjective. It never names or explicitly contrasts those siblings, so an agent must infer the differentiation.

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 guidance at all: nothing says to prefer word-noun when a noun is needed, nor when this general sampler is the right choice. Usage is only implied by the phrase 'random word', leaving selection against a dozen sibling word tools to inference.

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