Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-noun

Generates a random noun for use in fake data and test fixtures. Optionally specify a word length or a strategy to control which noun is returned.

Instructions

Returns a random noun.

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

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

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and mostly fails to: it doesn't say whether nouns come from a fixed fake-data word list or a dictionary, whether output is a plain string, whether results repeat, or whether any seeding is possible. Only the 'random' characteristic is disclosed.

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 zero wasted words. It is arguably over-terse rather than padded, which costs it nothing on conciseness but leaves the other dimensions thin.

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?

For a zero-required-parameter generator this is close to adequate, but with no output schema the description should state the return type (a string noun) and whether the underlying word list is real or synthetic. As written an agent must guess at the shape of the result.

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% and the single optional 'options' parameter is fully documented in the schema, including length bounds and the strategy enum. The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Returns a random noun" is a specific verb plus resource, so an agent knows exactly what it produces. It doesn't explicitly distinguish itself from siblings like word-adjective or word-verb, though the name and description together make the distinction near-obvious.

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?

The description offers no when-to-use guidance, no mention of alternatives such as word-verb or lorem-word, and no note about when random nouns are appropriate as placeholder data. Usage must be inferred entirely from the tool name.

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