Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-catchPhraseDescriptor

Generates a random catch phrase descriptor for display to end users, helping populate company catchphrases with varied wording.

Instructions

Returns a random catch phrase descriptor 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-catchPhraseDescriptor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior3/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. It does disclose the two key traits an agent needs: the result is randomized (non-deterministic) and is a user-displayable fragment, but it says nothing about output length, format, or whether the value is a single word or a multi-word phrase.

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 redundancy, sized appropriately for a trivial random-value generator.

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 no-parameter tool with no output schema, the description covers what is returned and that it is random, which is the minimum viable set. It falls short by not characterizing the descriptor itself (word vs phrase, capitalization, how it composes with the catchPhrase/adjective/noun siblings) in a crowded family of similar generators.

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 empty schema is fully consistent with the stated behavior. Baseline 4 applies for a parameterless tool.

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 catch phrase descriptor" gives a specific verb (returns/random) and a resource (catch phrase descriptor), which is enough to know it generates a text fragment. However, it never clarifies what a 'descriptor' is relative to the sibling adjective/noun/phrase generators, so the agent cannot fully distinguish it from company-catchPhraseAdjective or company-catchPhraseNoun.

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 phrase "can be displayed to an end user" implies usage as a display fragment, which is a weak but real usage hint. There is no explicit when-to-use rule, no note that this is a building block to combine with the other catch-phrase parts, and no exclusion of the sibling generators.

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