Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-buzzNoun

Returns a random buzz noun to demonstrate data being viewed by a manager. Generate placeholder business terms for mockups, demos, and test fixtures.

Instructions

Returns a random buzz noun that can be used to demonstrate data being viewed by a manager.

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": "company-buzzNoun"
  }
}

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 disclosure burden. It does disclose the key non-determinism ('random'), which is genuinely useful, but says nothing about the shape, casing, or word count of the returned string, nor whether repeated calls can repeat values.

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 front-loaded sentence with no filler or redundant restatement of the tool name. Every clause contributes either the return type, the randomness, or the intended use.

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 generator this is nearly sufficient: it states what is returned and that it is random. The only shortfall is the absence of any note on the string's format or predictability, which an agent might need when composing multi-word demo data.

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 there is nothing for the description to disambiguate; the schema baseline of 4 applies. The description adds no misleading pseudo-parameter information.

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 names a specific verb and resource ('Returns a random buzz noun'), so an agent knows exactly what value comes back. It does not explicitly contrast itself with the adjacent buzzAdjective / buzzVerb / buzzPhrase siblings, but the noun-vs-other-part-of-speech distinction is unambiguous from the text and name.

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: it says the value can be used to 'demonstrate data being viewed by a manager,' which signals placeholder/filler-data generation. There is no explicit when-to-use rule, no statement about when to prefer company-catchPhraseNoun or word-noun, and no exclusion conditions.

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