Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-buzzPhrase

Generate a random buzz phrase for demonstrating data views to managers in demos or mockups.

Instructions

Generates a random buzz phrase 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-buzzPhrase"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does disclose the key trait: output is random/non-deterministic, so repeated calls differ. It doesn't mention side effects or whether a format/seed can be controlled, but for a pure generator that is a minor gap.

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 stating the action, the result, and the intended use with no filler. Nothing could be removed without losing meaning.

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, the description says what it produces and why you'd call it, which is enough to invoke it correctly. Slightly more on output shape (e.g., a single string combining adjective/noun/verb) would make it fully self-contained.

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, which is the baseline 4 case; there is nothing the description needs to disambiguate. The empty schema and the description are consistent.

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 ('Generates') and resource ('a random buzz phrase'), so the agent knows exactly what comes back. It does not differentiate from the nearby buzzAdjective/buzzNoun/buzzVerb siblings that produce phrase components rather than a whole phrase, so it stops short of a 5.

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?

It offers one usage context ('demonstrate data being viewed by a manager'), which implies when the tool is appropriate. It never states when not to use it or points to the component-word siblings as alternatives, so guidance is implied rather than explicit.

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