Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-catchPhrase

Generates a random catchphrase for display to end users, supplying placeholder branding text for demos, mockups, or sample company content.

Instructions

Generates a random catch phrase that can be displayed to an end user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/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 disclosure burden, and it does state the key behavioral trait: output is random/non-deterministic, so repeated calls yield different results. It says nothing about result length, format, or whether output is safe for arbitrary display contexts, and there is no output schema to fill that gap.

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?

One front-loaded sentence with no filler; the core action comes first and the usage hint trails it. It is arguably under-specified rather than verbose, which is the more relevant risk here.

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 trivial zero-parameter generator this is close to adequate, but with no annotations and no output schema, an agent gets no signal about output shape or the relationship to the sibling component generators. That missing sibling context is the main completeness gap.

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 schema baseline of 4 applies and there is no parameter meaning for the description to add. The single sentence correctly implies a parameterless call.

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 uses a specific verb ("Generates") and resource ("a random catch phrase"), so the action is unambiguous. It does not distinguish this tool from the visible siblings company-catchPhraseAdjective/Descriptor/Noun or company-buzzPhrase, leaving an agent to infer that this returns a full phrase rather than a single word component.

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 phrase "can be displayed to an end user" hints at a user-facing context, but there is no explicit when-to-use guidance, no when-not-to-use conditions, and no routing to the closely related component tools or buzzPhrase alternative. An agent must guess whether it needs the whole phrase or its parts.

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