Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-buzzVerb

Generates a random corporate buzz verb for fake manager-facing data views. Use it to populate demo dashboards, reports, or presentations with realistic business language.

Instructions

Returns a random buzz verb 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-buzzVerb"
  }
}

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?

With no annotations, the description carries the full burden. It does disclose the one behavior that matters here — that the value is random, i.e. non-deterministic and likely different per call — but it doesn't say whether the return is a bare string or an object, or whether randomness is bounded to a fixed list.

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; the return type leads and the usage note follows. Nothing could be removed without losing information.

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 trivial zero-parameter generator with no output schema, the description covers what it returns and why it exists. The only real omission is the shape of the returned value, which the absent output schema would otherwise need to cover.

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 the baseline is 4. The description correctly implies no input is required and adds no misleading parameter talk.

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 ('Returns') and resource ('a random buzz verb'), so the agent knows exactly what comes back. It doesn't explicitly contrast with siblings like company-buzzNoun or company-buzzAdjective, but the word 'verb' in both name and description makes the distinction unambiguous in practice.

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?

The sentence 'can be used to demonstrate data being viewed by a manager' supplies a use context, which implies this is for demo/sample data generation. It stops short of stating when to prefer this over the noun/adjective/phrase variants or whether results are meant to be composed with them.

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